I agree with
reneeb that you need the extra '/' in the global substitution.
However, there's no reason for the backslashes in the regular expressions. Neither quotes (") nor commas (,) are
regular-expression metacharacters, so just write them like this:
while($_line1 =~ /"/) {
...
$_extraLine1 =~ s/,//g;
Is there some reason you're not using "use strict" and "use warnings"? They're very useful, and would point out the locations where you've neglected to create lexically-scoped variables with
my. You may also want to rethink the use of leading '_' in your variable names, which typically have the connotation of being a program-internal variable. And finally, do you really want the clutter of comments like:
}# End the check to see if contained another quote.
and
}# End while statement
in the code?
It's pretty easy to see where the opening '{' for each of them are; all the more so if you indent prudently and don't add unhelpful comments to the mix.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.