I’m saying if your use case makes regex the best option, you’ve gone the wrong way and should turn back. There are definitely corners you can paint yourself into that make it the way to go, but you’ve ended up there through a series of bad ideas.
Turns out the million hours of coding put into SQL, makes it a better option than regex, even for xml based files.
If you’re needing that level of complexity in a text file search, you already fucked up by putting the data in a text file. There’s a reason data file formats exist.
Never debug regex, just generate a new one. It’s not worth the hassle to figure out not only what it does, but what it was meant to do.
Better yet, just write it out in code, and never use regex. Tis a stupid thing that never should have been made.
Now I’m feeling called out. I keep having these stacks of if statements that could just be a big ass list of and and and, but then it runs into the debate of how much crap should be in one line of code? Especially knowing, at some point, it’s going to be my dumb ass stepping through trying to figure out why this one edge case is the reason we’re not hitting the inner code.
Have you read Microsoft manuals?
It’s not the language. ChatGPT is about as useful as a decent code manual. It won’t actually solve any problems for you, but it can show you the general format for doing so.
Look at you with your color vision being all elitist. Some of us old bastards don’t see them pretty rainbows so much any more.
It’s a law that was used to bring down mob bosses. It makes it illegal to have other people commit crimes for you.
Hopefully that link works, the text of the law is fairly clear as far as legal texts go.
So your use cases for regex are when you’re not going to actually fix the problem that caused you to need regex?