Ugh, I'm so silly. Even after I learned what
/o does at YAPC, from
Dominus.
I0's example answers the question.
As for what
/o does, it means "do not compile this again." What it does get that done is this:
print "trying...\n";
$x = qr/japhy/o;
print $you =~ $x;
# makes a tree like
[print "trying\n"]
[compile regex /japhy/]
[return regex (some internal form)]
[match regex on $you]
[print]
# the /o modifier tells [return regex] to MODIFY the tree
[print "trying\n"] -------------------\
[compile regex /japhy/] |
[return regex (some internal form)] <-/
[match regex on $you]
[print]
That's what happens. The op-tree is modified because of the
/o modifier. Perl never sees the "compile this regex" op again, and instead, it uses some pre-compiled regex.
japhy --
Perl and Regex Hacker
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.