First off, thank you for the reply. Silly being using a system() call. It's frowned upon in ansi c, most of our CGI's are written in ansi c, and my support programmer says system calls are expensive and the use of piping is preferred in C for the most part. (not that I have an opinion, I'm self taught and a number of things like that escape me)
Not to be too much of a newbie, but I don't really get how the above code avoids the shell? Does it still not shell the list? I'll implement that right now. I do prefer the look of it.
As for pretty XML I personally could care less as well, but when a client is paying and demands pretty XML with tabs and not spaces, which I will say, the use of tabs is quite a bit better for the huge xml files, my little test XML files with 2 spaces indenting 201k with 1 tab per indent it's 184k this will make a massive difference on the multi-megabyte XML files.
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.