Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

There are quite a few techniques you can use to make your regexen nicer, any combination of which might be useful to you, see for example /x, /e, /r, \K, and lookarounds in perlre. In the following example I've thrown all of them together into one, which may be overkill. (I see ikegami has posted something similar, albeit non-functional, while I was composing this.)

my $data = <<'END'; foo123bar # foo123bar foo456bar # xyz foo789bar abc foo456bar END $data =~ s{ ^ # beginning of line \h* \# \h* # comment lines \K # keep everything up to here in replacement (?<comment> \N*) # capture the comment $ # end of line } { handle_foobar( $+{comment} ) }msxge; sub handle_foobar { return shift =~ s{ foo \K (\d+) (?= bar ) }{ $1 =~ tr/0-9/a-j/r }msxger; }
I could turn the string into a line-list

Note it's also possible to open a string as an in-memory filehandle:

my $str = <<'END'; Hello # START World # END Aaa # START Bbb # END Ccc END open my $fh, '<', \$str or die $!; while (<$fh>) { chomp; if ( /^# START/ .. /^# END/ ) { print "<$_>\n"; } } close $fh;

Also, a more advanced regex technique is m/\G.../gc parsing, which is described in perlop. Also, as for your example here, if the delimiters need to be escaped, see Regexp::Common::delimited.

In reply to Re: s///g within m//g regions by haukex
in thread s///g within m//g regions by almr

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?

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

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (5)
As of 2023-09-28 06:48 GMT
Find Nodes?
    Voting Booth?

    No recent polls found