889
you are viewing a single comment's thread
view the rest of the comments
[-] frezik@midwest.social 31 points 1 week ago

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.

[-] marcos@lemmy.world 17 points 1 week ago

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.

[-] frezik@midwest.social 6 points 1 week ago

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.

https://wumpus-cave.net/post/2022/06/2022-06-06-how-to-write-regexes-that-are-almost-readable/index.html

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.

[-] tyler@programming.dev 10 points 1 week ago

wait... why do you have so many regexes you need to put them in a database???

[-] wise_pancake@lemmy.ca 5 points 1 week ago

The comments flag needs more support.

this post was submitted on 14 Feb 2025
889 points (98.5% liked)

Programmer Humor

20033 readers
1438 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS