regular expresions

wtf prog

What about them?

they're freaking obnoxious, that's what.

Only if you're a complete fucktard.

i guess that makes me a fucktard then.

I guess so.

Yeah, I don't get them either. It's like someone decided one day, oh hey, I'm going to build this thing which does pattern matching, and I'll make for it the most assinine syntax for it man has ever seen. It makes brainfuck look like English prose. Fuck regex

s/^([^,]+)(.).*([^ ]+) ([^ ]+)$/\4\2 \3 \1/

>>7
wtf, they're fucking simple as shit to understand. take a fucking course on computational theory and beat it fucking into your brain until you understand. how the fuck do you expect to write an ansi-compliant C compiler without even understanding regular expressions?

seriously. wtf.

>>8
Valid regex code

>>8
If you know there's always going to be a comma after the second atom, why not just use a comma as the third atom? That would reduce the number of backreferences needed. And if you don't know that, then this pattern has very different behavior in the comma and no-comma cases. The second atom is probably going to be too greedy without a comma (guessing, based on the .* in the middle; I don't know what application this was written for).

>>10
You need to turn in your programmer's license until you take a remedial course. That regex is fucking easy to mentally parse (though not exactly well-written).

>>11
It was to transform >>7, sillybuns.

>>13
regex, Fuck Yeah

[spoiler]
Let's talk about regex baby
Let's talk about you and me
Let's talk about all the good things
And the bad things that may be
Let's talk about regex
[/spoiler]

>>15

^{ＢＢＣＯＤＥ} _{ＦＡＩＬＵＲＥ}

Second item in a   GREAT COUNTRY OF   FREEDOM AND BROTHERHOOD   SHANGHAI CHINA ONE.

Don't change these.

Name:		Email:
Entire Thread Thread List