More seriously, the class of problem REs are idea for, which includes primarily:
Any spot need in Python or C# that I have to detect or extract specific patterns in a string
Using CLI tools in bash or writing shell scripts, it's not long before and RE in a grep or sed or such is called for.
Yeah, could be an age or generation thing but I call them REs not regexes so much.
Essentially REs fill the gap between:
The very basic string find, extract and split tools that many languages provide like like Excel does for example and basic string types in many modern languages provide
Full on grammar parsing.
In between these two extremes is a rich territory of spot pattern testing and string manipulation that a terse pattern definition language provides and the one that essentially came to dominate is called "regular" ;-), probably mainly because in its earliest inceptions it was designed and intended to be, supported by diverse tools in the *nix landscape of the day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My contexts for RE us in order of frequency of late:
What tools do I use? In order again:
What types of problems?
Yeah, could be an age or generation thing but I call them REs not regexes so much.
Essentially REs fill the gap between:
In between these two extremes is a rich territory of spot pattern testing and string manipulation that a terse pattern definition language provides and the one that essentially came to dominate is called "regular" ;-), probably mainly because in its earliest inceptions it was designed and intended to be, supported by diverse tools in the *nix landscape of the day.