regexp

If the regexp is expressing a concept that would otherwise take 20 lines of ad-hoc string processing in Java, I'll take the regexp.

I guess the question is where the regexp special vars are scoped to though, I see how that's not entirely clear.

A regexp is a very specialized way of express what a pattern must match, opossed to a java code that express how to perform the matching.

Is it easier to make a mistake and introduce a bug in a regexp, or in java code?

Is this a regexp vs strcmp() issue or is there something more subtle at play?

I have a regexp set up that immediately moves all incoming emails with no-reply to my spam folder.

I wrote the camelCaser in Google Websearch (basing it off Closure), and I used a simple regexp without memoization.

For example one that I did close to 30 years ago was move/copy utilities that used regexp.

To add, * Good regexp chops in a scripting language.

So don't underestimate the power of regexp when properly used...

- His treatment of camelCase is truly embarrassing, relying on an ugly RegExp every time it's called.

So it is a huge undertaking to rewrite something as complex as regexp to a completely new syntax and yet clearer and simpler to the majority of devs.

Back when I was playing with parsers in JS, the fastest approach to anything string-related was through RegExp, even trivial tasks like "first character is X".

I can give you like $30 for it and a puppy." <= in which the sender has sent mail to a list instead of a person and does not have a table for sale, even though it matches the regexp and provides a parseable price.