3 ms·
I've been making good use of http://www.regexper.com/ http://www.regexper.com/ since it was linked here. It's made learning regexes much easier as it gives a cl
by vacri 13y ago
I've been making good use of http://www.regexper.com/ http://www.regexper.com/ since it was linked here. It's made learning regexes much easier as it gives a clear workflow diagram.
For example, it showed that the horrible email regex in this article had a couple of errors - the dot before the TLD should be escaped (without the escape, it's 'any character'), and that group #1 can either be letters or digits, but not both (when it can be).
It's still not a good regex, since there are characters like hyphens, dots, and pluses that are valid pre-'@' characters, which both sample regexes fail to recognise.
- dyml 13y agoGreat resource, it seems immensly useful! I will be sure to investigate any errors on my part! :) And as I've said on the Github Repo, the library is not quite ready for prime time. When it's stable, i'll be sure to publish a nuget package for simple access.
- thiht 13y agoPersonally I use http://www.debuggex.com/ http://www.debuggex.com/ since it offers a step by step visualization, a live generation of the diagram, a live syntax checking of the regex, etc.
- harrytuttle 13y ago+1 for debuggex. This is the best tool I've seen and I've tried hundreds.
- vacri 13y agoJust playing around with it now, it's nice how it builds up the regex as you write it, but I did notice that it doesn't differentiate between '.' (match one character of any kind) and '\.' (the character for 'dot') Hrm, on a closer look, it affects all special characters (like ^ and $) and it does differentiate them, but only by turning them blue - makes it hard to see the change.