If you are developing generic subroutines, then the names
inside your subroutines aren't bad, but the fact that you
hard code the name of the file is. If you pass the in the
name of the file as an argument to the sub, then you will
have some reusable subroutines:
sub file_to_list {
my $name = shift or die "must have name to read";
open (FILE, '<', $name) or die "can't read from $name: $!";
chomp(my @data = <FILE>);
return @data;
}
sub list_to_file {
my $name = shift or die "must have name to write";
open (FILE, '>', $name) or die "can't write to $name: $!";
print FILE "$_\n" for @_;
}
my @foo = file_to_list('file.in');
print "$_\n" for @foo;
list_to_file('file.out',@foo);
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.