What is the reason for Visual Studio’s Find & Replace dialog regular expressions not following standard regex syntax, e.g. using :b instead of \s?
What is the reason for Visual Studio’s Find & Replace dialog regular expressions not
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the reason for Visual Studio’s Find & Replace dialog regular expressions not following standard regex syntax, e.g. using :b instead of \s?
Maybe for the same reason that Perl, Emacs, extended Regexps all have different ‘standard’ syntaxes (albeit mostly similar): they were all developed with different requirements. Emacs doesn’t seem to offer
\dfor instance for matching numeric digits. (arguably\disn’t ‘standard’, but is reasonably widely supported, so one might think that is was standard)There’s support for bidirectional and other unicode characters offers more control than what’s available in POSIX, plus there’s the rather useful
:iand:qas shortcuts for C/C++ identifiers and quoted strings. So the different syntax presumably grew out of the domain-specific requirements of VS.Net. More on the different things supported here.I agree that it is an annoyance to have a different syntax, but I also find it annoying to remember to type
[:digit:]rather than\dwhen I’m emacs.