regex 0.9.6

Together with the server move I released a new version my regex tool.

  • Improved logging.
  • Fixed problem where long text strings would not fix their “box”.
  • Fixed some typos.
  • Fixed some misc minor bugs.

At the moment only PHP PCRE, PHP POSIX and JavaScript are enabled. Hopefully I will get the other up and running soon too, but I need help from my host to get the problems solved.

Tags:

27 Responses to “regex 0.9.6”

  1. Jørund Ruud Says:

    Hei!
    Når jeg bruker verktøyet ditt under PHP preg_replace(), blir ikke innholdet i feltet replacement tatt med :D

  2. Lars Olav Torvik Says:

    Heisann.
    Takk for tilbakemeldingen. Viktig med tilbakemelding for at dette verktøyet skal fungere best mulig for alle som bruker det, meg inkludert :-)

    Det hadde sneket seg inn en feil ved preg_replace i forrige versjon. Denne feilen skal nå være rettet.

  3. ewall Says:

    Thanks, Lars, this is an excellent tool!

    I do have a question, though: It only refreshes/retries the match when I am on the “PHP PCRE” tab. If I type into the “Perl” tab, it doesn’t change to tell me if the regex matches or not. Is that the expected behavior?

  4. Lars Olav Torvik Says:

    I have some problems with the perl tester on the new server. I removed it for now. Hope to be able to reintroduce it again later when I get time to do some work on it.

  5. Chibani Says:

    Hi,
    I’ve been using your tools a few times. It’s a great tool to try regex ^^
    Unfortunately, it’s unavailable now …. May I help you hosting this project ?
    Don’t hesitate sending me an email if you’re interested ;)

    Best regards

  6. Lars Olav Torvik Says:

    Thanks for the offer hosting Chibani, but I think I’m good for now :-)

    The site was down earlier today, but everything should be back to normal now.

  7. Chibani Says:

    Ok,
    great job anyway ;)

  8. Jesse Says:

    Lars.. your regex tool is simply perfect… i have been using it since you published it.. have you thought about making a desktop or widget version? i would like to have it available offline .. incase of emergencies heh..

  9. MizardX Says:

    Could you allow multi-line regex’s when using the x-flag? Just swapping the input-box with a textarea works functionally. The exception is that the code-div don’t know how to deal with line-breaks.

  10. hiacynt Says:

    Hey Lars, just wanted to say how grateful I am to you for this great tool. Since I am new to regexing, it helped me greatly to refine my formulas until I finally understood how they should properly look like. Thanks a bunch!

  11. Rattus Says:

    Hi Lars,

    I like your RegEx tool, but I can’t find any way to change the pattern delimiters to a different character. It currently adds forward slashes automatically, whch breaks the XML parsing regex I am testing.

    Is this a limitation of v0.9.6?

  12. frqz Says:

    great regex tool mate, by now the best online i ve seen. has i everything i needed. thank you a lot!

  13. Mike Says:

    Thanks Lars, I’m grateful for this excellent tool.

    I feel it is the best regex tester available online.

    Mike

  14. Ryan Says:

    Have you ever considered adding a mod_rewrite tab? I use your tool A LOT and thought it would be a great addition.

  15. SeeDoubleYou Says:

    Thanks man, this tool is amazingly helpful. Got it bookmarked right away! Are their plans on releasing a next version, and if so, what’s going to be added?

  16. SeeDoubleYou Says:

    their = there in previous comment of course…

  17. Lars Olav Says:

    Hi all.
    As you can see this blog is not really used any more, but I do read all the comments that you write here. The blog will probably be replaced with something different in the future, but do not worry since it will not affect the regex tool!

    At the moment I do not have any concrete plans for new versions of the regex tool. It is tempting to do a big rewrite since the code is starting to get old, but it still works so I have postponed it so far. Some of the suggestions here would be great additions like the possibility to change the pattern delimiters. So feel free to keep posting ideas!

    We will see what I have time for. If I manage to find some extra “programming time” I might suprise us all with a new release ;-)

  18. Jacob Christiansen Says:

    Great tool. Great for developing regexps. Use it all the time. Keep up the good work.

  19. gark87 Says:

    This is strange behavior of highlighter with following parameters:

    PHP PCRE
    preg_match_all

    Pattern (start and end slashes will be added when needed):
    a+b*
    Subject:
    azab

    it highlights in Matches _a_z_a_b, but shouldn’t it be _a_z_ab_?
    Result looks right: (a, ab).

  20. Lucian Says:

    Hi,

    I am learning how to use the regular expressions (I program in PHP) and looking for a testing tool, I must say yours was the best out of the 3 I tested (the first 3 results in google). So, let me congratulate you for your work!
    There are anyway, some improvements (not bugs) that I can suggest you:
    - it is sometimes useful to see the error message (only when you get an error, not always!), eventually in the place where the “result” usually is placed.
    - the “Help PHP PCRE” is very long. I suggest you to place the symbol and the description on the same row, eventually with different colors, (like http://www.pagecolumn .com/tool/pregtest.htm).

    Thanks again for doing it and for not filling it with annoying banners!

  21. JCommelin Says:

    Hi Lars,

    Thanks for your very good regex tool.
    I wondered, could you add functionality so I can choose my delimeters myself? At the moment you can only use the default ‘/’ but that is not handy when prototyping a regex for pathnames. I would like to be able to change it to one of “@#$” for example.

    JCommelin

  22. Zamus Says:

    Thanks for the regex tool.

    add the following above the adword.

    If you like this tool, click on the advertisers!

    :D ;)

  23. oxman Says:

    Very nice one !

  24. Damien Says:

    Dear Lars,

    Thanks for a very useful, well designed tool. I truly helped me out debugging a complex pcre.

    One suggestion for improvement, the generated php code does not properly escape the backslash “\” and the single quote “‘”. For example: pattern ‘a+\\’b+’ on subject string ‘aaa\’bbb’ is coded as preg_match(’/'a+\\’b+’/', ”aaa\’bbb”, $result); but that code is not valid - it should be preg_match(’/\\\’a+\\\\\’b+\\\’/', ‘\’aaa\\\’bbb\”, $result);

  25. DaveDisaster Says:

    I use your regex tool on a regular basis. Incredibly useful utility, so thanks for the update.

    Seems to be a small issue with JavaScript code output for replace - the replacement string (or backref as the case may be) is not quoted, which will cause people problems if they copy/paste the code from your site.

    Keep up the good work!

  26. Ronnie Says:

    I also love to use this tool, it makes regular expressions less hard.

    I can confirm what DaveDisaster said about the quotes in the js version.

    I also noticed a small other problem:
    Pattern:
    Replacement:
    Subject:

    The tool detects the pattern in the string, but the replacement is not visible. When i remove the first “<” in the replacement sting it works as it should.

    When i use the < in real javascript it works.

  27. Ronnie Says:

    I also love to use this tool, it makes regular expressions less hard.

    I can confirm what DaveDisaster said about the quotes in the js version.

    I also noticed a small other problem:
    Pattern: “<meta charset=”(.*?)”/>”
    Replacement: “<meta http-equiv=”Content-Type” content=”text/html; charset=$1″ />”
    Subject: “<head><meta charset=”utf-8″/><title>”

    The tool detects the pattern in the string, but the replacement is not visible. When i remove the first “<” in the replacement sting it works as it should.

    When i use the < in real javascript it works.

    I see wordpress is filtering the HTML input so i replaced them with < and >

Leave a Reply

For spam filtering purposes, please copy the number 5723 to the field below: