deleted by creator
HOWD YOU GET MY PASSWORD?!?
deleted by creator
It helps if you break it apart into its component parts. Which is like anything else, really, but we’ve all accepted that regexes are supposed to run together in an unreadable mess. No reason it has to be that way.
If they are Perl regexes, like all regexes are supposed to be, you can have non-semantic whitespace and comments.
But if you are using some system that enforces something different, you are out of luck.
Not necessarily. For just debugging purposes, you can still break them up to help understand them. Even ignoring that, there are options in languages that don’t implement /x.
At my company we store our regex in the database with linebreaks in it, but when it’s actually called to be used those line breaks are stripped out. That way regex that looks for X can all be all on one line and actually readable.
wait… why do you have so many regexes you need to put them in a database???
My job is regex.
Ummmmmmmm
The comments flag needs more support.
Regexr.com is my go-to.
This is the one I use! Might have to look at regexer though
Downvoted so that everyone can know I’m cool since I understand regex better than the idiot who made that meme.
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.
Regex is a write only language.
If I have a complex regular expression to code into my app, I write it in pomsky, then copy paste the compiled regex to my source file, but also keep the pomsky source nearby. Much more maintainable.
Aziz! LIGHT!
Ohhhhh it was this extra ’
LOL yeah that’s about right.
This is basically code refactoring on a simplified level. You’re basically renaming a whole bunch of functions/tokens at once.
Let’s say you’re renaming the variable ‘count’ under the method ‘buttplug’. First off, what do you rename it to?
You start by replacing every instance of buttplug.count with a unique token, let’s say tnuoc.gulpttub.
Then you replace that buttplug with a unique buttplug.
Simple.
Then you replace that buttplug with a unique buttplug.
Rare buttplugs with good affixes are better than unique buttplugs.
There are no bugs, it’s just not doing what you expect it to be doing…
… which, now that I think of it, can be said about all software in general.
After fixing, now that you are expert, please migrate the regex to our new language.
I think he found the Road Runner.
awk-ward
Ffs just rewrite it
