This may not be the issue in this particular case, but it is an issue that you should address in your code: Always check the return values of system calls.
What does that mean? It means, when you ask Perl to open a file, you should check to be sure that the file actually got opened. Here is how that is often accomplished:
open OUTFILE, '>', 'pretty.xml'
or die "Couldn't open pretty.xml for output:\n$!\n";
# ... and later...
close OUTFILE
or die "Couldn't close output file, pretty.xml:\n$!\n";
Also notice, within your open command you are using the concatenation operator, '.', when it's actually better in this case to use the comma.
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.