- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
I know I’m weird, but I love regex.
Downvoted so that everyone can know I’m cool since I understand regex better than the idiot who made that meme.
LOL yeah that’s about right.
awk-ward
I usually do
# What we are doing (high level) # Why we need regex # Regex step by step # Examples of matches regexAnd I still rewrite it the next time
// abandon all hope ye who commit here (?:[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])*")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-]*[a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])+)\])Edith: damit, Not the first to post this abomination
I haven’t laughed so hard in a month. Thank you for that.
Ffs just rewrite it
Me checking my own docs: “this is some voodoo shit, idk how it works”
That’s what my comments say
I found your email address:
(?:[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])*")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-]*[a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])+)\])I was about to ruin your day by finding a valid email address that would be rejected by your regex, but it doesn’t even parse correctly on regex101.com
The only valid regex for email is
.+@.+btwWhat about
"user@not_domain"? It validates but isn’t valid - there’s no domain part, theis quotedThat’s not something you can determine using a regex.
“user@com” for example could be a perfectly working email.
The right way is to send a verification email in every case.
Does this regex include
"very.(),:;<>[]\".VERY.\"very@\\ \"very\".unusual".example.comWhere did you get that “RFC standard” regex? It doesn’t allow domain names with one component RFC5321
Neither does it allow spaces in quoted string, as per RFC5322
This, 👋@✉️.gg, is already a working email address in most clients and if RFC6532 ever gets accepted, it would be officially recognized as such.
My point isn’t to make your regex bad, just that it doesn’t validate or invalidate an email properly. Nothing stops me from giving you and invalid but syntactically correct email after all.
You have to send an email anyways to verify, so the most you can check is the presence of one @ symbol.The argument here is that checking complex validation is a fool’s errand. Yes, you can write a fully validating regex for RFC email. In fact, it should be possible to write a regex shorter than the one that gets passed around since the 90s, because regular expression engines support recursive patterns now. (Part of the reason that old regex is so complicated is because email allows nested comments (which is insane (how insane? (Lisp levels insane)))).
However, it doesn’t get you much of anywhere. What you really want to know is if it’s a valid email or not, and the only way to do that is to send an email to that address with a confirmation. The only point of the regex is to throw away obviously bad addresses. For that, checking that there’s an @ symbol and something for the user and domain portions is sufficient. I’d add needing a dot in the domain portion, but it’s not that important.
Classically, it was argued that emails don’t even need a domain portion when things are done for internal systems, or that internal domains don’t need a tld. In my personal experience, this is rarely done anymore and can be safely ignored. Maybe some very, very old legacy systems, and if you’re working on one of those, then sure. For everyone else, don’t worry about it. You’re probably working on publicly accessible systems, and even if you’re not, most users are going to prefer using their fully spec’d out email address, anyway.
Cool story bro, go argue with the IETF
Why? Do you think nested comments are a good idea?
Deleted by user.
HOWD YOU GET MY PASSWORD?!?
Appropriate username.
That
\\.part doesn’t look right, but what do I know. Apparently control codes are valid elsewhere, so a literal backslash followed by any character, even a space or a newline, might actually be valid there.“Yeah, my e-mail address is abc, carriage return, three backspaces and a terminal bell at example dot com. … What do you mean your mail program doesn’t support it?”
I have found chatgpt to be very good at writing regex. I also don’t know how to write regex.
well, you won’t get better using chatgpt for it
In my experience, it is good at simple to medium complexity regex. For the harder ones it starts being quite useless though, at best providing a decent starting point to begin debugging from.
Aziz! LIGHT!
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
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.
I love regex and I use it a lot, but I very rarely use it in any kind of permanent solution. When I do, I make sure to keep it as minimal as possible, supplementing with higher level programming where possible. Backreferences and assertions are a cardinal sin and should never be used.
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.
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.
