315
submitted 8 months ago by mac@programming.dev to c/comics@programming.dev

Hover Text:

Wait, forgot to escape a space. Wheeeeee[taptaptap]eeeeee!

Transcript

[in a yellow box:]
Whenever I learn a new skill I concoct elaborate fantasy scenarios where it lets me save the day.

Megan: Oh no! The killer must have followed her on vacation!
[Megan points to computer.]
Megan: But to find them we'd have to search through 200 MB of emails looking for something formatted like an address!
Cueball: It's hopeless!

Off-panel voice: Everybody stand back.

Off-panel voice: I know regular expressions.

[A man swings in on a rope, toward the computer.]

tap tap
The word PERL! appears in a bubble.

[The man swings away, and the other characters cheer.]

you are viewing a single comment's thread
view the rest of the comments
[-] hemko@lemmy.dbzer0.com 19 points 8 months ago
[-] elvith@feddit.de 16 points 8 months ago

Who's gonna tell them? I'd do it but I'm still busy parsing HTML with regex.... it's working any minute now!

[-] otacon239@feddit.de 2 points 8 months ago

What am I missing? I typically used it as a sanity check and would vet the changes. Never as a one-click modify. Or is there something else I should know about?

[-] Feathercrown@lemmy.world 4 points 8 months ago* (last edited 8 months ago)

This short article has some good examples at the top: https://sigparser.com/developers/email-parsing/regex-validate-email-address/

Basically, you can very easily make a regex to match 99% of email addresses, but technically an email could be something like "!@[124.35.6.72]"

[-] otacon239@feddit.de 6 points 8 months ago

Ah, yeah. It was never meant to be a be all and all. Just something to clean up the complete trash before I started proofreading. Besides, these were emails the customer provided and could easily be changed afterwords. Their fault if we get bad emails in the list ¯\_(ツ)_/¯

[-] Feathercrown@lemmy.world 3 points 8 months ago

This is the way

[-] elvith@feddit.de 1 points 8 months ago* (last edited 8 months ago)

You're completely correct. In practice, it's usually good enough to just check for ".+@.+" or ".+@.+\..+". Why? It's broad enough to allow almost everything and it rejects the most obvious typos. And in the end, the final verification would be to send an email there which contains a link, that one has to click to finalize the signup/change. Even if you had a regex that could filter every possible adress that's possible according to the standard, you still wouldn't know whether it really exists.

[-] dev_null@lemmy.ml 4 points 8 months ago

I wrote a regex that matches 100% of email addresses and had no problems using it. It's ".+@.+"

[-] Feathercrown@lemmy.world 1 points 8 months ago* (last edited 8 months ago)

Meme aside that's what I'd use tbh. Or the ultimate email validation: just sending the signup email and if they typed an invalid email it won't send

this post was submitted on 01 Feb 2024
315 points (98.5% liked)

Comics

436 readers
1 users here now

A community for sharing comics related to programming

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 8 months ago
MODERATORS