Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I used split to parse a simple comma-delimited text string (i.e. no embedded commas, no quoted values, etc) into an array variable and the last values in the text string were all null. It is important for my process to maintain the null (or undefined) entries in the array, however it appears that split does not create array entries (even undef entries) for trailing null entries in the text string. This is not at all the behavior I expected from split and I can find no way to work around it, other than appending a throw-away character to the end of the text string prior to splitting it, which seems awfully kludgey. I tried adding a limit number equal to the total number of entries I expected (including the trailing null entries), but it had no effect. Can anyone shed some light on split's behavior and/or suggest a cleaner work around? Thanks in advance. Sample code follows ...

#!/usr/bin/perl -w use strict; my $txt = 'a,b,c,d,,,,,,'; my @fld = split(/,/,$txt); print "\$txt = |$txt|\n"; print "\@fld = |@fld|\n"; for (0 .. $#fld) {print "\$fld\[", $_, "\] = |$fld[$_]|\n"}; __END__ Results: -------- $txt = |a,b,c,d,,,,,,| @fld = |a b c d| $fld[0] = |a| $fld[1] = |b| $fld[2] = |c| $fld[3] = |d|

"Its not how hard you work, its how much you get done."


In reply to Fooled By Split by roho

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.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (12)
As of 2024-04-23 08:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found