Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Good morrow!

I like your way of generating your regex. While some of us might be quicker to just think a minute, and then write down a fully working regex, your step-by-step way makes sure you don't miss anything. *makes mental note to keep this method in mind*

Using the /o modifier may indeed make for speed, as it allows only one compilation. The variables within your pattern will be interpolated (unless your delimiters are single quotes), and thus your pattern may be recompiled, whenever the pattern operator is evaluated. The /o modifier prevents this recompilation and thus may save time.

You are using qr// with your regex, and then use it standalone-ingly to match against $_. That won't work, because qr//, while specifying a pattern, does not match against anything. Instead, the regex is compiled and returned for future use.

The reason why your $regex1 doesn't match probably lies in what Django stated above. I can't really say, however, why placing your /x at different places would make a difference...

Hope this helps...

--cs

There are nights when the wolves are silent and only the moon howls. - George Carlin


In reply to Re: Improving my regex skills and a few questions. by schumi
in thread Improving my regex skills and a few questions. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (4)
As of 2024-04-19 20:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found