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

comment on

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

If efficiency is defined by keystrokes, you may save a few by using capturing parens in your split. You may also rely on the fact that the -n flag loads one line at a time into $_, and that split looks at $_ if no other string param is provided:

echo |perl -lnE 'say reverse + split /(\.)/'

So this is 36 keystrokes if you start counting after the pipe. Someone will probably beat it though. One way to beat it will be eliminating two unneeded whitespace characters, so this gets it down to 34:

echo |perl -lnE'say reverse +split/(\.)/'

If efficiency is defined by some other metric, you would probably need to benchmark a few alternatives according to that metric to determine which one wins.


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

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.