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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
