If nothing else, the ability to take an existing regex written by someone else years ago, dump it into the program and have it show it as a tree structure makes it staggeringly easier to debug.
I don't like GUIs / fluffy hand holding programs. I'm prepared to believe this is an irrational prejudice and actually this is a much easier way to deal with regex. Then again, if it isn't BBC BASIC I think it's too fluffy and modern ;-)
I started with a BBC B, back in 1983 (I think). Lovely piece of kit.
And I am _so_ not coding in anything other than a lovely IDE. And the thought of going back to actually remembering what method names are called fills me with horror.
Is there such a thing as a lovely IDE? I've yet to find one that doesn't fail on totally basic text editing UI or have a crapton of fiddly buttons with totally mysterious icons. In other words, they all look too much like KDE!
Visual Studio is lovely. Works fine for basic typing, while also allowing me to press a button and go direct to the source of a method call, debug things really nicely, underlining errors, completing variable names, and refactoring code nicely.
I have to freely admit that I really do like VS's debugging, and Intellisense is the best implementation of autocompleting that I've ever seen.
Having said that, it 'feels' wrong to me as an editor, and I almost always work in a language where intellisense would be exactly equivalent to the plain old symbol-name autocomplete that I have in EMACS.
Actually I guess that's not strictly true, I also work a lot in Perl and Python, but in Python I just use dir() in an interactive session and it tells me everything I need to know.
Visual Studio is lovely. I use NetBeans 7 right now, but because it's based on Java, it's dog slow in a way that slow dogs would be embarrassed to be associated with (while still being faster than Eclipse).
I've never found anything I really like for non .NET stuff - instead, I use an IDE until I get to the end of my tether with it, and move onto the next one. I can sort of see why people use vim, although that's always felt like seven shades of awful to me too.
If there was an IDE that just worked for my purposes, and did so well, I'd pay a thousand pounds for it, easily. Until then, a combination of things that don't quite work and Google gets me through.
I'd also say "Ergh", but because "[o]ur goal is to make Expresso the best .NET regular expression development tool on the planet" makes it rather pointless for me and their "it's free but we will nag you until you give us your email address" thing would a bit grumpy-making if I were going to install it.
(There's probably more than a little "in my day we wrote our regexps uphill in the snow both ways and we LIKED it", as well.)
Heh, any I write that are longer than a dozen characters or a bit hairy I explode like that. Because I know I'll need to understand them in 6 months' time.
Then add white space etc. to them yourself. Build a test suite with enough data extracted from the wild that you're confident that you're not breaking the regex, if it's complicated enough.
If you're having difficulty, the correct thing to do is to use a regexp species that is sufficiently expressive that it can incorporate whitespace, indentation, and if necessary multiline comments. Like Perl's been doing for the past fifteen years.
I have said a couple of times that as there are a relatively small number of people in this world capable of growing facial hair, and as facial hair is so awesome, it is the moral imperative for everyone capable of growing it, to do so. That way I'm surrounded by as much awesome and varied facial foliage as possible.
The name thing: depends on the form of wrong. If they use my slightly less preferred variant of my first name, no harm no foul; if they call me something that's definitely not my name, I'll correct them.
I agree with the variation. I used to work wiht someone who occassionally called me Cassie, because of my surname (plus she was old) so I didn't really mind.
Otherwise, my SEWIWEIC is that I'd probably quite quickly find a reason to send them an email and maybe subtly make them realise.
Beards: Depends on the beard and the face it's attached to. Neck beards are almost always bad, and beard with no mustache are generally inadvisable. :)
Regex: Not sure, as I've never actually worked with them and am not 100% clear on what they are and what they're used for. :)
Jeffrey Friedl's Mastering Regular Expressions is a must-read if you're working with them. You could try the valid email address matcher at the end with the GUI programme ;-)
I said editing regexes is crazy, but only because I find them so unreadable that I would prefer to get the plain English translation of what it's meant to do and then rewrite the damn thing from scratch.
Beards: good but I find them too scratchy on myself. I also start to find I want to wash my face after every meal.
Name correction: depends on the place and my current mood. Sometimes I ignore and feel annoyed. Sometimes I correct. When the same person gets it wrong several times I start to give up and consider them to be a cretin. This is especially true when they spell it wrong in emails, which are *replies to my emails which have my name in*.
Not completely true cos I do vaguely know what a regular expression is (mostly because Rob owns this shirt and periodically has to explain it to people. But I wouldn't know how to edit one.
Most beards are bad. For example, almost every single student/nerd who has ever grown one especially neckbeards or wild unkempt ones) Or did you mean that kind of beard that I might be in a relationship with? I like those.
I don't know what a regular expression is.
If someone got my name wrong, I would deliberately get theirs wrong. This happens a lot with emails at work - one of the companies we email all format their email addresses as surname dot firstname, but ours are the reverse. Even when a colleague of mine has a first name that is an actual name and a weird surname, this company has a tendency to use the person's surname as if it's a first name. So we just do the same when we reply :-D They've never yet called us out on it (probably because they think we're being dicks)
I liked my beard, but it got too itchy so I now have some stubble - mostly because properly shaving seems an utterly shit plan.
Having just got the hang of Visual Basic [ugh] and C++ [YAY!!], I'm not quite brave enough to look into what reg ex's are yet.
I often tell people my name is Tim, purely so I can say "There are some who call me.... Tim". In general I'm happy to play along if someone gets my name wrong. I went by a nickname for so long it barely matters.
I have a rare name, but confusingly my manager's name is only one letter different. I correct people if they call me by my manager's name, but otherwise don't care.
I used to default to beards = BAD but the Boy grew one and it's very flattering indeed so I find I have now mellowed to them a lot and started finding them attractive on other people too. They have to be proper neat, shaped beards though, none of this scruffy, straggly and unkempt, I-just-can't-be-arsed-shaving nonsense.
I am crap at names and would therefore correct the person because I'd be mortified if I got someone's name wrong and they went off in a huff rather than correcting me.
I have a few hundred-character regexps hanging around. I don't have much problem figuring out what they're doing by looking at them.
When someone gets my name wrong, I generally don't do or say anything about it. My dentist has been calling me by my technically correct first name that nobody ever calls me for over 10 years, because I never corrected him. The catering manager at work often calls me Mark, although she sometimes does get my name right too, so correcting her wouldn't have much point. I just treat it as a quirk of interacting with someone, like if they have an unusual accent or something.
no subject
no subject
no subject
no subject
If nothing else, the ability to take an existing regex written by someone else years ago, dump it into the program and have it show it as a tree structure makes it staggeringly easier to debug.
no subject
no subject
And I am _so_ not coding in anything other than a lovely IDE. And the thought of going back to actually remembering what method names are called fills me with horror.
no subject
no subject
no subject
I've tried Eclipse and NetBeans and they're both dire.
no subject
no subject
no subject
no subject
Having said that, it 'feels' wrong to me as an editor, and I almost always work in a language where intellisense would be exactly equivalent to the plain old symbol-name autocomplete that I have in EMACS.
no subject
no subject
I've never found anything I really like for non .NET stuff - instead, I use an IDE until I get to the end of my tether with it, and move onto the next one. I can sort of see why people use vim, although that's always felt like seven shades of awful to me too.
If there was an IDE that just worked for my purposes, and did so well, I'd pay a thousand pounds for it, easily. Until then, a combination of things that don't quite work and Google gets me through.
no subject
(There's probably more than a little "in my day we wrote our regexps uphill in the snow both ways and we LIKED it", as well.)
no subject
no subject
$regex = '@
\s+ # match some initial whitespace
( \w+ ) # capture the first word
@';
and so on.
no subject
no subject
*insert rant about shoddy coders here*
no subject
I'd be shocked if there wasn't something like that already: give it a V8 regexp, and it'll spit it out nicely formatted in /x format.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
But there does seem to be a societal presumption against them at the moment, so I'm voting GOOD, in order to even things up.
no subject
And of course, the world is all about me.
no subject
no subject
Otherwise, my SEWIWEIC is that I'd probably quite quickly find a reason to send them an email and maybe subtly make them realise.
Or, you know, this: http://www.youtube.com/watch?v=fN4_NiCIdcw
Lizzie (just so's you know) xx
no subject
Regex: Not sure, as I've never actually worked with them and am not 100% clear on what they are and what they're used for. :)
no subject
no subject
no subject
http://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags/1732454#1732454
no subject
I tried posting the Frield email regex, but it was too long for Livejournal
no subject
no subject
no subject
Name correction: depends on the place and my current mood. Sometimes I ignore and feel annoyed. Sometimes I correct. When the same person gets it wrong several times I start to give up and consider them to be a cretin. This is especially true when they spell it wrong in emails, which are *replies to my emails which have my name in*.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
Most beards are bad. For example, almost every single student/nerd who has ever grown one especially neckbeards or wild unkempt ones) Or did you mean that kind of beard that I might be in a relationship with? I like those.
I don't know what a regular expression is.
If someone got my name wrong, I would deliberately get theirs wrong. This happens a lot with emails at work - one of the companies we email all format their email addresses as surname dot firstname, but ours are the reverse. Even when a colleague of mine has a first name that is an actual name and a weird surname, this company has a tendency to use the person's surname as if it's a first name. So we just do the same when we reply :-D They've never yet called us out on it (probably because they think we're being dicks)
no subject
Having just got the hang of Visual Basic [ugh] and C++ [YAY!!], I'm not quite brave enough to look into what reg ex's are yet.
I often tell people my name is Tim, purely so I can say "There are some who call me.... Tim". In general I'm happy to play along if someone gets my name wrong. I went by a nickname for so long it barely matters.
no subject
no subject
I am crap at names and would therefore correct the person because I'd be mortified if I got someone's name wrong and they went off in a huff rather than correcting me.
no subject
When someone gets my name wrong, I generally don't do or say anything about it. My dentist has been calling me by my technically correct first name that nobody ever calls me for over 10 years, because I never corrected him. The catering manager at work often calls me Mark, although she sometimes does get my name right too, so correcting her wouldn't have much point. I just treat it as a quirk of interacting with someone, like if they have an unusual accent or something.
no subject