comment on

Thanks for all the replies, helped a lot.

@choroba - the test code as given didn't help me much... guessing I need to read up on Test::More. Using qr// - I have now picked that up, cheers.

@AnomalousMonk - had to read it twice but now I know the result was what it was not because 'the computer doesn't like me' ;) Thanks.

@Athanasius - I added the first ? quatifier so the expression matches 10-99, didn't indeed realise it introduces an unexpected match as well ...

@Crackers - spotted and fixed the above, cheers :)

@graff - all the spotting and fixing of errors above makes your case indeed... my take on it would be that regexp are good as long as you don't get in deeper than you can easily troubleshoot yourself out of, and that (getting in too deep) is very easily done.

@Discipulus - yes I am reinventing ipv4 address matching, partially as an excercise. Thanks for the links, heading over there now.

In reply to Re^4: Is this a bug in perl regex engine or in my brain? by nikmit
in thread Is this a bug in perl regex engine or in my brain? by nikmit

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks