I suggest you modify recurse($node, $depth) to accept a 3rd parameter: a scalar to contain the filehandle to print to. For example: recurse($node, $depth, $fh_to_print_to). (Although I find most subs that print to file rather than returning a string of results, bad form. But that's just me.)
Then modify all print statements in recurse() to utilise provided filehandle, rather that printing to the default: STDOUT.
Then open the file to write results to, prior to first calling recurse(). And supply it to recurse(). Close the filehandle once the first call to recurse() returns.
And you're done.
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.