Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

The race is on....

This shaves two strokes off my previous version.

# -2 strokes: echo www.perlmonks.org.split.reduce.code.check |perl -lF'(\.)' -E'say +reverse@F' # Compare to: echo www.perlmonks.org.split.reduce.code.check |perl -lnE'say reverse +split/(\.)/'

-F'pattern' sets -a auto-split mode with the pattern specified. The auto-split goes into @F. The -F field also sets -n automatically. So the original version and this version work essentially the same way, just relying on different ways to specify the split.


Dave


In reply to Re^2: split string using optimized code or perl one liner by davido
in thread split string using optimized code or perl one liner by madtoperl

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.