Now that I have that under control...
If 'that' refers to the lack code tags in your OP, the situation is still out of control. A <code> tag is closed by a </code> tag, not by a </c> tag. Please see Markup in the Monastery. Please check the effects of your changes.
Printing to a file usually involves supplying an output file handle (see open) to the print statement. E.g.:
my $filename = 'file.name';
open my $fh_out, '>', $filename or die "opening '$filename': $!";
my $something_to_output_to_file = your_process();
print $fh_out "here is something for the file \n";
print $fh_out $something_to_output_to_file;
print $fh_out "that's all, folks! \n";
close $fh_out or die "closing '$filename': $!";
Please consider re-reading the answers you have been given in this and related threads. Please consider using lexical filehandles (as in the example given above). See also autodie.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||