Reminder: The use of “\” as a regex escape character is causing me problems in a particular coding scenario, see here: https://www.tbray.org/ongoing/When/202x/2024/09/22/Unbackslashing
Here’s the second round of polling on the “\” replacement, for the win.
Example regexp: “\([^\n\r)]*\)”
Previous poll: https://cosocial.ca/@timbray/113210605202526746
4/4 Poll 3 of 3: I want to choose another character to replace “\”, let’s use
“\([^\n\r)]*\)” as an example.
3/4 Poll 2 of 3. I want to choose another character to replace “\”, let’s use
“\([^\n\r)]*\)” as an example.
2/4 Poll 1 of 3. I want to choose another character to replace “\”, let’s use
“\([^\n\r)]*\)” as an example.
1/4 Reminder: The use of “\” as a regex escape character is causing me problems in a particular programming scenario, explained here: https://www.tbray.org/ongoing/When/202x/2024/09/22/Unbackslashing
As promised, here is a series of polls to let you, Dear Readers, vote on the “\” replacement, appearing as a comment thread on this post.
1st round has 3 polls. If they’re not here yet when you see this, come back in a bit.
Few strata of geekery are more obsessive than regular-expression geekery. So let’s have some fun! In https://www.tbray.org/ongoing/When/202x/2024/09/22/Unbackslashing I explain why using the usual backslash “\” for escaping is hellishly inconvenient in a current project and propose replacing it with one of «, —, “, ¶, §, or ~. This Friday, I’ll be running some polls tagged #unbackslash to let you all join in.
Tim Bray
Julian Reschke
lasersailor (he/him)