Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I will definitely take it under advisement and look into the modules others have developed for this porpoise,
but in the spirit of learning please advise me on using split. I am now trying your code Trantor like so:
#!/usr/local/bin/perl -w use strict; my $line = "a whole lotta shakin >pattern here< goin on"; my @bits_and_pieces = split /></, $line; print @bits_and_pieces;

Done this way the out put is the same as $line was originally:
a whole lotta shakin >pattern here< goin on
But if I use
my $line = "a whole lotta shakin ><pattern here>< goin on";
Then my output is: a whole lotta shakin pattern here goin on
The only thing that happened was my delimiters were deleted.
Would some kind soul explain why split did that.
I read perlfunc:split but I'm afraid I am no wiser.

In reply to Re: Re: Cropping the output of the pattern matcher by jerrygarciuh
in thread Cropping the output of the pattern matcher by jerrygarciuh

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.