.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "PERLFAQ5 1"
.TH PERLFAQ5 1 2023-11-28 "perl v5.38.2" "Perl Programmers Reference Guide"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
perlfaq5 \- Files and Formats
.SH VERSION
.IX Header "VERSION"
version 5.20210520
.SH DESCRIPTION
.IX Header "DESCRIPTION"
This section deals with I/O and the "f" issues: filehandles, flushing,
formats, and footers.
.SS "How do I flush/unbuffer an output filehandle? Why must I do this?"
.IX Xref "flush buffer unbuffer autoflush"
.IX Subsection "How do I flush/unbuffer an output filehandle? Why must I do this?"
(contributed by brian d foy)
.PP
You might like to read Mark Jason Dominus's "Suffering From Buffering"
at <http://perl.plover.com/FAQs/Buffering.html> .
.PP
Perl normally buffers output so it doesn't make a system call for every
bit of output. By saving up output, it makes fewer expensive system calls.
For instance, in this little bit of code, you want to print a dot to the
screen for every line you process to watch the progress of your program.
Instead of seeing a dot for every line, Perl buffers the output and you
have a long wait before you see a row of 50 dots all at once:
.PP
.Vb 4
\&    # long wait, then row of dots all at once
\&    while( <> ) {
\&        print ".";
\&        print "\en" unless ++$count % 50;
\&
\&        #... expensive line processing operations
\&    }
.Ve
.PP
To get around this, you have to unbuffer the output filehandle, in this
case, \f(CW\*(C`STDOUT\*(C'\fR. You can set the special variable \f(CW$|\fR to a true value
(mnemonic: making your filehandles "piping hot"):
.PP
.Vb 1
\&    $|++;
\&
\&    # dot shown immediately
\&    while( <> ) {
\&        print ".";
\&        print "\en" unless ++$count % 50;
\&
\&        #... expensive line processing operations
\&    }
.Ve
.PP
The \f(CW$|\fR is one of the per-filehandle special variables, so each
filehandle has its own copy of its value. If you want to merge
standard output and standard error for instance, you have to unbuffer
each (although STDERR might be unbuffered by default):
.PP
.Vb 7
\&    {
\&        my $previous_default = select(STDOUT);  # save previous default
\&        $|++;                                   # autoflush STDOUT
\&        select(STDERR);
\&        $|++;                                   # autoflush STDERR, to be sure
\&        select($previous_default);              # restore previous default
\&    }
\&
\&    # now should alternate . and +
\&    while( 1 ) {
\&        sleep 1;
\&        print STDOUT ".";
\&        print STDERR "+";
\&        print STDOUT "\en" unless ++$count % 25;
\&    }
.Ve
.PP
Besides the \f(CW$|\fR special variable, you can use \f(CW\*(C`binmode\*(C'\fR to give
your filehandle a \f(CW\*(C`:unix\*(C'\fR layer, which is unbuffered:
.PP
.Vb 1
\&    binmode( STDOUT, ":unix" );
\&
\&    while( 1 ) {
\&        sleep 1;
\&        print ".";
\&        print "\en" unless ++$count % 50;
\&    }
.Ve
.PP
For more information on output layers, see the entries for \f(CW\*(C`binmode\*(C'\fR
and open in perlfunc, and the PerlIO module documentation.
.PP
If you are using IO::Handle or one of its subclasses, you can
call the \f(CW\*(C`autoflush\*(C'\fR method to change the settings of the
filehandle:
.PP
.Vb 3
\&    use IO::Handle;
\&    open my( $io_fh ), ">", "output.txt";
\&    $io_fh\->autoflush(1);
.Ve
.PP
The IO::Handle objects also have a \f(CW\*(C`flush\*(C'\fR method. You can flush
the buffer any time you want without auto-buffering
.PP
.Vb 1
\&    $io_fh\->flush;
.Ve
.SS "How do I change, delete, or insert a line in a file, or append to the beginning of a file?"
.IX Xref "file, editing"
.IX Subsection "How do I change, delete, or insert a line in a file, or append to the beginning of a file?"
(contributed by brian d foy)
.PP
The basic idea of inserting, changing, or deleting a line from a text
file involves reading and printing the file to the point you want to
make the change, making the change, then reading and printing the rest
of the file. Perl doesn't provide random access to lines (especially
since the record input separator, \f(CW$/\fR, is mutable), although modules
such as Tie::File can fake it.
.PP
A Perl program to do these tasks takes the basic form of opening a
file, printing its lines, then closing the file:
.PP
.Vb 2
\&    open my $in,  \*(Aq<\*(Aq,  $file      or die "Can\*(Aqt read old file: $!";
\&    open my $out, \*(Aq>\*(Aq, "$file.new" or die "Can\*(Aqt write new file: $!";
\&
\&    while( <$in> ) {
\&            print $out $_;
\&    }
\&
\&    close $out;
.Ve
.PP
Within that basic form, add the parts that you need to insert, change,
or delete lines.
.PP
To prepend lines to the beginning, print those lines before you enter
the loop that prints the existing lines.
.PP
.Vb 2
\&    open my $in,  \*(Aq<\*(Aq,  $file      or die "Can\*(Aqt read old file: $!";
\&    open my $out, \*(Aq>\*(Aq, "$file.new" or die "Can\*(Aqt write new file: $!";
\&
\&    print $out "# Add this line to the top\en"; # <\-\-\- HERE\*(AqS THE MAGIC
\&
\&    while( <$in> ) {
\&            print $out $_;
\&    }
\&
\&    close $out;
.Ve
.PP
To change existing lines, insert the code to modify the lines inside
the \f(CW\*(C`while\*(C'\fR loop. In this case, the code finds all lowercased
versions of "perl" and uppercases them. The happens for every line, so
be sure that you're supposed to do that on every line!
.PP
.Vb 2
\&    open my $in,  \*(Aq<\*(Aq,  $file      or die "Can\*(Aqt read old file: $!";
\&    open my $out, \*(Aq>\*(Aq, "$file.new" or die "Can\*(Aqt write new file: $!";
\&
\&    print $out "# Add this line to the top\en";
\&
\&    while( <$in> ) {
\&        s/\eb(perl)\eb/Perl/g;
\&        print $out $_;
\&    }
\&
\&    close $out;
.Ve
.PP
To change only a particular line, the input line number, \f(CW$.\fR, is
useful. First read and print the lines up to the one you  want to
change. Next, read the single line you want to change, change it, and
print it. After that, read the rest of the lines and print those:
.PP
.Vb 4
\&    while( <$in> ) { # print the lines before the change
\&        print $out $_;
\&        last if $. == 4; # line number before change
\&    }
\&
\&    my $line = <$in>;
\&    $line =~ s/\eb(perl)\eb/Perl/g;
\&    print $out $line;
\&
\&    while( <$in> ) { # print the rest of the lines
\&        print $out $_;
\&    }
.Ve
.PP
To skip lines, use the looping controls. The \f(CW\*(C`next\*(C'\fR in this example
skips comment lines, and the \f(CW\*(C`last\*(C'\fR stops all processing once it
encounters either \f(CW\*(C`_\|_END_\|_\*(C'\fR or \f(CW\*(C`_\|_DATA_\|_\*(C'\fR.
.PP
.Vb 5
\&    while( <$in> ) {
\&        next if /^\es+#/;             # skip comment lines
\&        last if /^_\|_(END|DATA)_\|_$/;  # stop at end of code marker
\&        print $out $_;
\&    }
.Ve
.PP
Do the same sort of thing to delete a particular line by using \f(CW\*(C`next\*(C'\fR
to skip the lines you don't want to show up in the output. This
example skips every fifth line:
.PP
.Vb 4
\&    while( <$in> ) {
\&        next unless $. % 5;
\&        print $out $_;
\&    }
.Ve
.PP
If, for some odd reason, you really want to see the whole file at once
rather than processing line-by-line, you can slurp it in (as long as
you can fit the whole thing in memory!):
.PP
.Vb 2
\&    open my $in,  \*(Aq<\*(Aq,  $file      or die "Can\*(Aqt read old file: $!"
\&    open my $out, \*(Aq>\*(Aq, "$file.new" or die "Can\*(Aqt write new file: $!";
\&
\&    my $content = do { local $/; <$in> }; # slurp!
\&
\&        # do your magic here
\&
\&    print $out $content;
.Ve
.PP
Modules such as Path::Tiny and Tie::File can help with that
too. If you can, however, avoid reading the entire file at once. Perl
won't give that memory back to the operating system until the process
finishes.
.PP
You can also use Perl one-liners to modify a file in-place. The
following changes all 'Fred' to 'Barney' in \fIinFile.txt\fR, overwriting
the file with the new contents. With the \f(CW\*(C`\-p\*(C'\fR switch, Perl wraps a
\&\f(CW\*(C`while\*(C'\fR loop around the code you specify with \f(CW\*(C`\-e\*(C'\fR, and \f(CW\*(C`\-i\*(C'\fR turns
on in-place editing. The current line is in \f(CW$_\fR. With \f(CW\*(C`\-p\*(C'\fR, Perl
automatically prints the value of \f(CW$_\fR at the end of the loop. See
perlrun for more details.
.PP
.Vb 1
\&    perl \-pi \-e \*(Aqs/Fred/Barney/\*(Aq inFile.txt
.Ve
.PP
To make a backup of \f(CW\*(C`inFile.txt\*(C'\fR, give \f(CW\*(C`\-i\*(C'\fR a file extension to add:
.PP
.Vb 1
\&    perl \-pi.bak \-e \*(Aqs/Fred/Barney/\*(Aq inFile.txt
.Ve
.PP
To change only the fifth line, you can add a test checking \f(CW$.\fR, the
input line number, then only perform the operation when the test
passes:
.PP
.Vb 1
\&    perl \-pi \-e \*(Aqs/Fred/Barney/ if $. == 5\*(Aq inFile.txt
.Ve
.PP
To add lines before a certain line, you can add a line (or lines!)
before Perl prints \f(CW$_\fR:
.PP
.Vb 1
\&    perl \-pi \-e \*(Aqprint "Put before third line\en" if $. == 3\*(Aq inFile.txt
.Ve
.PP
You can even add a line to the beginning of a file, since the current
line prints at the end of the loop:
.PP
.Vb 1
\&    perl \-pi \-e \*(Aqprint "Put before first line\en" if $. == 1\*(Aq inFile.txt
.Ve
.PP
To insert a line after one already in the file, use the \f(CW\*(C`\-n\*(C'\fR switch.
It's just like \f(CW\*(C`\-p\*(C'\fR except that it doesn't print \f(CW$_\fR at the end of
the loop, so you have to do that yourself. In this case, print \f(CW$_\fR
first, then print the line that you want to add.
.PP
.Vb 1
\&    perl \-ni \-e \*(Aqprint; print "Put after fifth line\en" if $. == 5\*(Aq inFile.txt
.Ve
.PP
To delete lines, only print the ones that you want.
.PP
.Vb 1
\&    perl \-ni \-e \*(Aqprint if /d/\*(Aq inFile.txt
.Ve
.SS "How do I count the number of lines in a file?"
.IX Xref "file, counting lines lines line"
.IX Subsection "How do I count the number of lines in a file?"
(contributed by brian d foy)
.PP
Conceptually, the easiest way to count the lines in a file is to
simply read them and count them:
.PP
.Vb 2
\&    my $count = 0;
\&    while( <$fh> ) { $count++; }
.Ve
.PP
You don't really have to count them yourself, though, since Perl
already does that with the \f(CW$.\fR variable, which is the current line
number from the last filehandle read:
.PP
.Vb 2
\&    1 while( <$fh> );
\&    my $count = $.;
.Ve
.PP
If you want to use \f(CW$.\fR, you can reduce it to a simple one-liner,
like one of these:
.PP
.Vb 1
\&    % perl \-lne \*(Aq} print $.; {\*(Aq    file
\&
\&    % perl \-lne \*(AqEND { print $. }\*(Aq file
.Ve
.PP
Those can be rather inefficient though. If they aren't fast enough for
you, you might just read chunks of data and count the number of
newlines:
.PP
.Vb 6
\&    my $lines = 0;
\&    open my($fh), \*(Aq<:raw\*(Aq, $filename or die "Can\*(Aqt open $filename: $!";
\&    while( sysread $fh, $buffer, 4096 ) {
\&        $lines += ( $buffer =~ tr/\en// );
\&    }
\&    close $fh;
.Ve
.PP
However, that doesn't work if the line ending isn't a newline. You
might change that \f(CW\*(C`tr///\*(C'\fR to a \f(CW\*(C`s///\*(C'\fR so you can count the number of
times the input record separator, \f(CW$/\fR, shows up:
.PP
.Vb 6
\&    my $lines = 0;
\&    open my($fh), \*(Aq<:raw\*(Aq, $filename or die "Can\*(Aqt open $filename: $!";
\&    while( sysread $fh, $buffer, 4096 ) {
\&        $lines += ( $buffer =~ s|$/||g; );
\&    }
\&    close $fh;
.Ve
.PP
If you don't mind shelling out, the \f(CW\*(C`wc\*(C'\fR command is usually the
fastest, even with the extra interprocess overhead. Ensure that you
have an untainted filename though:
.PP
.Vb 1
\&    #!perl \-T
\&
\&    $ENV{PATH} = undef;
\&
\&    my $lines;
\&    if( $filename =~ /^([0\-9a\-z_.]+)\ez/ ) {
\&        $lines = \`/usr/bin/wc \-l $1\`
\&        chomp $lines;
\&    }
.Ve
.SS "How do I delete the last N lines from a file?"
.IX Xref "lines file"
.IX Subsection "How do I delete the last N lines from a file?"
(contributed by brian d foy)
.PP
The easiest conceptual solution is to count the lines in the
file then start at the beginning and print the number of lines
(minus the last N) to a new file.
.PP
Most often, the real question is how you can delete the last N lines
without making more than one pass over the file, or how to do it
without a lot of copying. The easy concept is the hard reality when
you might have millions of lines in your file.
.PP
One trick is to use File::ReadBackwards, which starts at the end of
the file. That module provides an object that wraps the real filehandle
to make it easy for you to move around the file. Once you get to the
spot you need, you can get the actual filehandle and work with it as
normal. In this case, you get the file position at the end of the last
line you want to keep and truncate the file to that point:
.PP
.Vb 1
\&    use File::ReadBackwards;
\&
\&    my $filename = \*(Aqtest.txt\*(Aq;
\&    my $Lines_to_truncate = 2;
\&
\&    my $bw = File::ReadBackwards\->new( $filename )
\&        or die "Could not read backwards in [$filename]: $!";
\&
\&    my $lines_from_end = 0;
\&    until( $bw\->eof or $lines_from_end == $Lines_to_truncate ) {
\&        print "Got: ", $bw\->readline;
\&        $lines_from_end++;
\&    }
\&
\&    truncate( $filename, $bw\->tell );
.Ve
.PP
The File::ReadBackwards module also has the advantage of setting
the input record separator to a regular expression.
.PP
You can also use the Tie::File module which lets you access
the lines through a tied array. You can use normal array operations
to modify your file, including setting the last index and using
\&\f(CW\*(C`splice\*(C'\fR.
.ie n .SS "How can I use Perl's ""\-i"" option from within a program?"
.el .SS "How can I use Perl's \f(CW\-i\fP option from within a program?"
.IX Xref "-i in-place"
.IX Subsection "How can I use Perl's -i option from within a program?"
\&\f(CW\*(C`\-i\*(C'\fR sets the value of Perl's \f(CW$^I\fR variable, which in turn affects
the behavior of \f(CW\*(C`<>\*(C'\fR; see perlrun for more details. By
modifying the appropriate variables directly, you can get the same
behavior within a larger program. For example:
.PP
.Vb 10
\&    # ...
\&    {
\&        local($^I, @ARGV) = (\*(Aq.orig\*(Aq, glob("*.c"));
\&        while (<>) {
\&            if ($. == 1) {
\&                print "This line should appear at the top of each file\en";
\&            }
\&            s/\eb(p)earl\eb/${1}erl/i;        # Correct typos, preserving case
\&            print;
\&            close ARGV if eof;              # Reset $.
\&        }
\&    }
\&    # $^I and @ARGV return to their old values here
.Ve
.PP
This block modifies all the \f(CW\*(C`.c\*(C'\fR files in the current directory,
leaving a backup of the original data from each file in a new
\&\f(CW\*(C`.c.orig\*(C'\fR file.
.SS "How can I copy a file?"
.IX Xref "copy file, copy File::Copy"
.IX Subsection "How can I copy a file?"
(contributed by brian d foy)
.PP
Use the File::Copy module. It comes with Perl and can do a
true copy across file systems, and it does its magic in
a portable fashion.
.PP
.Vb 1
\&    use File::Copy;
\&
\&    copy( $original, $new_copy ) or die "Copy failed: $!";
.Ve
.PP
If you can't use File::Copy, you'll have to do the work yourself:
open the original file, open the destination file, then print
to the destination file as you read the original. You also have to
remember to copy the permissions, owner, and group to the new file.
.SS "How do I make a temporary file name?"
.IX Xref "file, temporary"
.IX Subsection "How do I make a temporary file name?"
If you don't need to know the name of the file, you can use \f(CWopen()\fR
with \f(CW\*(C`undef\*(C'\fR in place of the file name. In Perl 5.8 or later, the
\&\f(CWopen()\fR function creates an anonymous temporary file:
.PP
.Vb 1
\&    open my $tmp, \*(Aq+>\*(Aq, undef or die $!;
.Ve
.PP
Otherwise, you can use the File::Temp module.
.PP
.Vb 1
\&    use File::Temp qw/ tempfile tempdir /;
\&
\&    my $dir = tempdir( CLEANUP => 1 );
\&    ($fh, $filename) = tempfile( DIR => $dir );
\&
\&    # or if you don\*(Aqt need to know the filename
\&
\&    my $fh = tempfile( DIR => $dir );
.Ve
.PP
The File::Temp has been a standard module since Perl 5.6.1. If you
don't have a modern enough Perl installed, use the \f(CW\*(C`new_tmpfile\*(C'\fR
class method from the IO::File module to get a filehandle opened for
reading and writing. Use it if you don't need to know the file's name:
.PP
.Vb 3
\&    use IO::File;
\&    my $fh = IO::File\->new_tmpfile()
\&        or die "Unable to make new temporary file: $!";
.Ve
.PP
If you're committed to creating a temporary file by hand, use the
process ID and/or the current time-value. If you need to have many
temporary files in one process, use a counter:
.PP
.Vb 6
\&    BEGIN {
\&        use Fcntl;
\&        use File::Spec;
\&        my $temp_dir  = File::Spec\->tmpdir();
\&        my $file_base = sprintf "%d\-%d\-0000", $$, time;
\&        my $base_name = File::Spec\->catfile($temp_dir, $file_base);
\&
\&        sub temp_file {
\&            my $fh;
\&            my $count = 0;
\&            until( defined(fileno($fh)) || $count++ > 100 ) {
\&                $base_name =~ s/\-(\ed+)$/"\-" . (1 + $1)/e;
\&                # O_EXCL is required for security reasons.
\&                sysopen $fh, $base_name, O_WRONLY|O_EXCL|O_CREAT;
\&            }
\&
\&            if( defined fileno($fh) ) {
\&                return ($fh, $base_name);
\&            }
\&            else {
\&                return ();
\&            }
\&        }
\&    }
.Ve
.SS "How can I manipulate fixed-record-length files?"
.IX Xref "fixed-length file, fixed-length records"
.IX Subsection "How can I manipulate fixed-record-length files?"
The most efficient way is using \fBpack()\fR and
\&\fBunpack()\fR. This is faster than using
\&\fBsubstr()\fR when taking many, many strings. It is
slower for just a few.
.PP
Here is a sample chunk of code to break up and put back together again
some fixed-format input lines, in this case from the output of a normal,
Berkeley-style ps:
.PP
.Vb 10
\&    # sample input line:
\&    #   15158 p5  T      0:00 perl /home/tchrist/scripts/now\-what
\&    my $PS_T = \*(AqA6 A4 A7 A5 A*\*(Aq;
\&    open my $ps, \*(Aq\-|\*(Aq, \*(Aqps\*(Aq;
\&    print scalar <$ps>;
\&    my @fields = qw( pid tt stat time command );
\&    while (<$ps>) {
\&        my %process;
\&        @process{@fields} = unpack($PS_T, $_);
\&        for my $field ( @fields ) {
\&            print "$field: <$process{$field}>\en";
\&        }
\&        print \*(Aqline=\*(Aq, pack($PS_T, @process{@fields} ), "\en";
\&    }
.Ve
.PP
We've used a hash slice in order to easily handle the fields of each row.
Storing the keys in an array makes it easy to operate on them as a
group or loop over them with \f(CW\*(C`for\*(C'\fR. It also avoids polluting the program
with global variables and using symbolic references.
.SS "How can I make a filehandle local to a subroutine? How do I pass filehandles between subroutines? How do I make an array of filehandles?"
.IX Xref "filehandle, local filehandle, passing filehandle, reference"
.IX Subsection "How can I make a filehandle local to a subroutine? How do I pass filehandles between subroutines? How do I make an array of filehandles?"
As of perl5.6, \fBopen()\fR autovivifies file and directory handles
as references if you pass it an uninitialized scalar variable.
You can then pass these references just like any other scalar,
and use them in the place of named handles.
.PP
.Vb 1
\&    open my    $fh, $file_name;
\&
\&    open local $fh, $file_name;
\&
\&    print $fh "Hello World!\en";
\&
\&    process_file( $fh );
.Ve
.PP
If you like, you can store these filehandles in an array or a hash.
If you access them directly, they aren't simple scalars and you
need to give \f(CW\*(C`print\*(C'\fR a little help by placing the filehandle
reference in braces. Perl can only figure it out on its own when
the filehandle reference is a simple scalar.
.PP
.Vb 1
\&    my @fhs = ( $fh1, $fh2, $fh3 );
\&
\&    for( $i = 0; $i <= $#fhs; $i++ ) {
\&        print {$fhs[$i]} "just another Perl answer, \en";
\&    }
.Ve
.PP
Before perl5.6, you had to deal with various typeglob idioms
which you may see in older code.
.PP
.Vb 3
\&    open FILE, "> $filename";
\&    process_typeglob(   *FILE );
\&    process_reference( \e*FILE );
\&
\&    sub process_typeglob  { local *FH = shift; print FH  "Typeglob!" }
\&    sub process_reference { local $fh = shift; print $fh "Reference!" }
.Ve
.PP
If you want to create many anonymous handles, you should
check out the Symbol or IO::Handle modules.
.SS "How can I use a filehandle indirectly?"
.IX Xref "filehandle, indirect"
.IX Subsection "How can I use a filehandle indirectly?"
An indirect filehandle is the use of something other than a symbol
in a place that a filehandle is expected. Here are ways
to get indirect filehandles:
.PP
.Vb 5
\&    $fh =   SOME_FH;       # bareword is strict\-subs hostile
\&    $fh =  "SOME_FH";      # strict\-refs hostile; same package only
\&    $fh =  *SOME_FH;       # typeglob
\&    $fh = \e*SOME_FH;       # ref to typeglob (bless\-able)
\&    $fh =  *SOME_FH{IO};   # blessed IO::Handle from *SOME_FH typeglob
.Ve
.PP
Or, you can use the \f(CW\*(C`new\*(C'\fR method from one of the IO::* modules to
create an anonymous filehandle and store that in a scalar variable.
.PP
.Vb 2
\&    use IO::Handle;                     # 5.004 or higher
\&    my $fh = IO::Handle\->new();
.Ve
.PP
Then use any of those as you would a normal filehandle. Anywhere that
Perl is expecting a filehandle, an indirect filehandle may be used
instead. An indirect filehandle is just a scalar variable that contains
a filehandle. Functions like \f(CW\*(C`print\*(C'\fR, \f(CW\*(C`open\*(C'\fR, \f(CW\*(C`seek\*(C'\fR, or
the \f(CW\*(C`<FH>\*(C'\fR diamond operator will accept either a named filehandle
or a scalar variable containing one:
.PP
.Vb 4
\&    ($ifh, $ofh, $efh) = (*STDIN, *STDOUT, *STDERR);
\&    print $ofh "Type it: ";
\&    my $got = <$ifh>
\&    print $efh "What was that: $got";
.Ve
.PP
If you're passing a filehandle to a function, you can write
the function in two ways:
.PP
.Vb 4
\&    sub accept_fh {
\&        my $fh = shift;
\&        print $fh "Sending to indirect filehandle\en";
\&    }
.Ve
.PP
Or it can localize a typeglob and use the filehandle directly:
.PP
.Vb 4
\&    sub accept_fh {
\&        local *FH = shift;
\&        print  FH "Sending to localized filehandle\en";
\&    }
.Ve
.PP
Both styles work with either objects or typeglobs of real filehandles.
(They might also work with strings under some circumstances, but this
is risky.)
.PP
.Vb 2
\&    accept_fh(*STDOUT);
\&    accept_fh($handle);
.Ve
.PP
In the examples above, we assigned the filehandle to a scalar variable
before using it. That is because only simple scalar variables, not
expressions or subscripts of hashes or arrays, can be used with
built-ins like \f(CW\*(C`print\*(C'\fR, \f(CW\*(C`printf\*(C'\fR, or the diamond operator. Using
something other than a simple scalar variable as a filehandle is
illegal and won't even compile:
.PP
.Vb 4
\&    my @fd = (*STDIN, *STDOUT, *STDERR);
\&    print $fd[1] "Type it: ";                           # WRONG
\&    my $got = <$fd[0]>                                  # WRONG
\&    print $fd[2] "What was that: $got";                 # WRONG
.Ve
.PP
With \f(CW\*(C`print\*(C'\fR and \f(CW\*(C`printf\*(C'\fR, you get around this by using a block and
an expression where you would place the filehandle:
.PP
.Vb 3
\&    print  { $fd[1] } "funny stuff\en";
\&    printf { $fd[1] } "Pity the poor %x.\en", 3_735_928_559;
\&    # Pity the poor deadbeef.
.Ve
.PP
That block is a proper block like any other, so you can put more
complicated code there. This sends the message out to one of two places:
.PP
.Vb 3
\&    my $ok = \-x "/bin/cat";
\&    print { $ok ? $fd[1] : $fd[2] } "cat stat $ok\en";
\&    print { $fd[ 1+ ($ok || 0) ]  } "cat stat $ok\en";
.Ve
.PP
This approach of treating \f(CW\*(C`print\*(C'\fR and \f(CW\*(C`printf\*(C'\fR like object methods
calls doesn't work for the diamond operator. That's because it's a
real operator, not just a function with a comma-less argument. Assuming
you've been storing typeglobs in your structure as we did above, you
can use the built-in function named \f(CW\*(C`readline\*(C'\fR to read a record just
as \f(CW\*(C`<>\*(C'\fR does. Given the initialization shown above for \f(CW@fd\fR, this
would work, but only because \fBreadline()\fR requires a typeglob. It doesn't
work with objects or strings, which might be a bug we haven't fixed yet.
.PP
.Vb 1
\&    $got = readline($fd[0]);
.Ve
.PP
Let it be noted that the flakiness of indirect filehandles is not
related to whether they're strings, typeglobs, objects, or anything else.
It's the syntax of the fundamental operators. Playing the object
game doesn't help you at all here.
.SS "How can I open a filehandle to a string?"
.IX Xref "string open IO::String filehandle"
.IX Subsection "How can I open a filehandle to a string?"
(contributed by Peter J. Holzer, hjp\-usenet2@hjp.at)
.PP
Since Perl 5.8.0 a file handle referring to a string can be created by
calling open with a reference to that string instead of the filename.
This file handle can then be used to read from or write to the string:
.PP
.Vb 3
\&    open(my $fh, \*(Aq>\*(Aq, \e$string) or die "Could not open string for writing";
\&    print $fh "foo\en";
\&    print $fh "bar\en";    # $string now contains "foo\enbar\en"
\&
\&    open(my $fh, \*(Aq<\*(Aq, \e$string) or die "Could not open string for reading";
\&    my $x = <$fh>;    # $x now contains "foo\en"
.Ve
.PP
With older versions of Perl, the IO::String module provides similar
functionality.
.SS "How can I set up a footer format to be used with \fBwrite()\fP?"
.IX Xref "footer"
.IX Subsection "How can I set up a footer format to be used with write()?"
There's no builtin way to do this, but perlform has a couple of
techniques to make it possible for the intrepid hacker.
.SS "How can I \fBwrite()\fP into a string?"
.IX Xref "write, into a string"
.IX Subsection "How can I write() into a string?"
(contributed by brian d foy)
.PP
If you want to \f(CW\*(C`write\*(C'\fR into a string, you just have to <open> a
filehandle to a string, which Perl has been able to do since Perl 5.6:
.PP
.Vb 2
\&    open FH, \*(Aq>\*(Aq, \emy $string;
\&    write( FH );
.Ve
.PP
Since you want to be a good programmer, you probably want to use a lexical
filehandle, even though formats are designed to work with bareword filehandles
since the default format names take the filehandle name. However, you can
control this with some Perl special per-filehandle variables: \f(CW$^\fR, which
names the top-of-page format, and \f(CW$~\fR which shows the line format. You have
to change the default filehandle to set these variables:
.PP
.Vb 1
\&    open my($fh), \*(Aq>\*(Aq, \emy $string;
\&
\&    { # set per\-filehandle variables
\&        my $old_fh = select( $fh );
\&        $~ = \*(AqANIMAL\*(Aq;
\&        $^ = \*(AqANIMAL_TOP\*(Aq;
\&        select( $old_fh );
\&    }
\&
\&    format ANIMAL_TOP =
\&     ID  Type    Name
\&    .
\&
\&    format ANIMAL =
\&    @##   @<<<    @<<<<<<<<<<<<<<
\&    $id,  $type,  $name
\&    .
.Ve
.PP
Although write can work with lexical or package variables, whatever variables
you use have to scope in the format. That most likely means you'll want to
localize some package variables:
.PP
.Vb 4
\&    {
\&        local( $id, $type, $name ) = qw( 12 cat Buster );
\&        write( $fh );
\&    }
\&
\&    print $string;
.Ve
.PP
There are also some tricks that you can play with \f(CW\*(C`formline\*(C'\fR and the
accumulator variable \f(CW$^A\fR, but you lose a lot of the value of formats
since \f(CW\*(C`formline\*(C'\fR won't handle paging and so on. You end up reimplementing
formats when you use them.
.SS "How can I output my numbers with commas added?"
.IX Xref "number, commify"
.IX Subsection "How can I output my numbers with commas added?"
(contributed by brian d foy and Benjamin Goldberg)
.PP
You can use Number::Format to separate places in a number.
It handles locale information for those of you who want to insert
full stops instead (or anything else that they want to use,
really).
.PP
This subroutine will add commas to your number:
.PP
.Vb 5
\&    sub commify {
\&        local $_  = shift;
\&        1 while s/^([\-+]?\ed+)(\ed{3})/$1,$2/;
\&        return $_;
\&    }
.Ve
.PP
This regex from Benjamin Goldberg will add commas to numbers:
.PP
.Vb 1
\&    s/(^[\-+]?\ed+?(?=(?>(?:\ed{3})+)(?!\ed))|\eG\ed{3}(?=\ed))/$1,/g;
.Ve
.PP
It is easier to see with comments:
.PP
.Vb 11
\&    s/(
\&        ^[\-+]?             # beginning of number.
\&        \ed+?               # first digits before first comma
\&        (?=                # followed by, (but not included in the match) :
\&            (?>(?:\ed{3})+) # some positive multiple of three digits.
\&            (?!\ed)         # an *exact* multiple, not x * 3 + 1 or whatever.
\&        )
\&        |                  # or:
\&        \eG\ed{3}            # after the last group, get three digits
\&        (?=\ed)             # but they have to have more digits after them.
\&    )/$1,/xg;
.Ve
.SS "How can I translate tildes (~) in a filename?"
.IX Xref "tilde tilde expansion"
.IX Subsection "How can I translate tildes (~) in a filename?"
Use the <> (\f(CWglob()\fR) operator, documented in perlfunc.
Versions of Perl older than 5.6 require that you have a shell
installed that groks tildes. Later versions of Perl have this feature
built in. The File::KGlob module (available from CPAN) gives more
portable glob functionality.
.PP
Within Perl, you may use this directly:
.PP
.Vb 11
\&    $filename =~ s{
\&      ^ ~             # find a leading tilde
\&      (               # save this in $1
\&          [^/]        # a non\-slash character
\&                *     # repeated 0 or more times (0 means me)
\&      )
\&    }{
\&      $1
\&          ? (getpwnam($1))[7]
\&          : ( $ENV{HOME} || $ENV{LOGDIR} )
\&    }ex;
.Ve
.SS "How come when I open a file read-write it wipes it out?"
.IX Xref "clobber read-write clobbering truncate truncating"
.IX Subsection "How come when I open a file read-write it wipes it out?"
Because you're using something like this, which truncates the file
\&\fIthen\fR gives you read-write access:
.PP
.Vb 1
\&    open my $fh, \*(Aq+>\*(Aq, \*(Aq/path/name\*(Aq; # WRONG (almost always)
.Ve
.PP
Whoops. You should instead use this, which will fail if the file
doesn't exist:
.PP
.Vb 1
\&    open my $fh, \*(Aq+<\*(Aq, \*(Aq/path/name\*(Aq; # open for update
.Ve
.PP
Using ">" always clobbers or creates. Using "<" never does
either. The "+" doesn't change this.
.PP
Here are examples of many kinds of file opens. Those using \f(CW\*(C`sysopen\*(C'\fR
all assume that you've pulled in the constants from Fcntl:
.PP
.Vb 1
\&    use Fcntl;
.Ve
.PP
To open file for reading:
.PP
.Vb 2
\&    open my $fh, \*(Aq<\*(Aq, $path                               or die $!;
\&    sysopen my $fh, $path, O_RDONLY                       or die $!;
.Ve
.PP
To open file for writing, create new file if needed or else truncate old file:
.PP
.Vb 3
\&    open my $fh, \*(Aq>\*(Aq, $path                               or die $!;
\&    sysopen my $fh, $path, O_WRONLY|O_TRUNC|O_CREAT       or die $!;
\&    sysopen my $fh, $path, O_WRONLY|O_TRUNC|O_CREAT, 0666 or die $!;
.Ve
.PP
To open file for writing, create new file, file must not exist:
.PP
.Vb 2
\&    sysopen my $fh, $path, O_WRONLY|O_EXCL|O_CREAT        or die $!;
\&    sysopen my $fh, $path, O_WRONLY|O_EXCL|O_CREAT, 0666  or die $!;
.Ve
.PP
To open file for appending, create if necessary:
.PP
.Vb 3
\&    open my $fh, \*(Aq>>\*(Aq, $path                              or die $!;
\&    sysopen my $fh, $path, O_WRONLY|O_APPEND|O_CREAT      or die $!;
\&    sysopen my $fh, $path, O_WRONLY|O_APPEND|O_CREAT, 0666 or die $!;
.Ve
.PP
To open file for appending, file must exist:
.PP
.Vb 1
\&    sysopen my $fh, $path, O_WRONLY|O_APPEND              or die $!;
.Ve
.PP
To open file for update, file must exist:
.PP
.Vb 2
\&    open my $fh, \*(Aq+<\*(Aq, $path                              or die $!;
\&    sysopen my $fh, $path, O_RDWR                         or die $!;
.Ve
.PP
To open file for update, create file if necessary:
.PP
.Vb 2
\&    sysopen my $fh, $path, O_RDWR|O_CREAT                 or die $!;
\&    sysopen my $fh, $path, O_RDWR|O_CREAT, 0666           or die $!;
.Ve
.PP
To open file for update, file must not exist:
.PP
.Vb 2
\&    sysopen my $fh, $path, O_RDWR|O_EXCL|O_CREAT          or die $!;
\&    sysopen my $fh, $path, O_RDWR|O_EXCL|O_CREAT, 0666    or die $!;
.Ve
.PP
To open a file without blocking, creating if necessary:
.PP
.Vb 2
\&    sysopen my $fh, \*(Aq/foo/somefile\*(Aq, O_WRONLY|O_NDELAY|O_CREAT
\&        or die "can\*(Aqt open /foo/somefile: $!":
.Ve
.PP
Be warned that neither creation nor deletion of files is guaranteed to
be an atomic operation over NFS. That is, two processes might both
successfully create or unlink the same file! Therefore O_EXCL
isn't as exclusive as you might wish.
.PP
See also perlopentut.
.SS "Why do I sometimes get an ""Argument list too long"" when I use <*>?"
.IX Xref "argument list too long"
.IX Subsection "Why do I sometimes get an ""Argument list too long"" when I use <*>?"
The \f(CW\*(C`<>\*(C'\fR operator performs a globbing operation (see above).
In Perl versions earlier than v5.6.0, the internal \fBglob()\fR operator forks
\&\fBcsh\fR\|(1) to do the actual glob expansion, but
csh can't handle more than 127 items and so gives the error message
\&\f(CW\*(C`Argument list too long\*(C'\fR. People who installed tcsh as csh won't
have this problem, but their users may be surprised by it.
.PP
To get around this, either upgrade to Perl v5.6.0 or later, do the glob
yourself with \fBreaddir()\fR and patterns, or use a module like File::Glob,
one that doesn't use the shell to do globbing.
.SS "How can I open a file named with a leading "">"" or trailing blanks?"
.IX Xref "filename, special characters"
.IX Subsection "How can I open a file named with a leading "">"" or trailing blanks?"
(contributed by Brian McCauley)
.PP
The special two-argument form of Perl's \fBopen()\fR function ignores
trailing blanks in filenames and infers the mode from certain leading
characters (or a trailing "|"). In older versions of Perl this was the
only version of \fBopen()\fR and so it is prevalent in old code and books.
.PP
Unless you have a particular reason to use the two-argument form you
should use the three-argument form of \fBopen()\fR which does not treat any
characters in the filename as special.
.PP
.Vb 2
\&    open my $fh, "<", "  file  ";  # filename is "   file   "
\&    open my $fh, ">", ">file";     # filename is ">file"
.Ve
.SS "How can I reliably rename a file?"
.IX Xref "rename mv move file, rename"
.IX Subsection "How can I reliably rename a file?"
If your operating system supports a proper \fBmv\fR\|(1) utility or its
functional equivalent, this works:
.PP
.Vb 1
\&    rename($old, $new) or system("mv", $old, $new);
.Ve
.PP
It may be more portable to use the File::Copy module instead.
You just copy to the new file to the new name (checking return
values), then delete the old one. This isn't really the same
semantically as a \f(CWrename()\fR, which preserves meta-information like
permissions, timestamps, inode info, etc.
.SS "How can I lock a file?"
.IX Xref "lock file, lock flock"
.IX Subsection "How can I lock a file?"
Perl's builtin \fBflock()\fR function (see perlfunc for details) will call
\&\fBflock\fR\|(2) if that exists, \fBfcntl\fR\|(2) if it doesn't (on perl version 5.004 and
later), and \fBlockf\fR\|(3) if neither of the two previous system calls exists.
On some systems, it may even use a different form of native locking.
Here are some gotchas with Perl's \fBflock()\fR:
.IP 1. 4
Produces a fatal error if none of the three system calls (or their
close equivalent) exists.
.IP 2. 4
\&\fBlockf\fR\|(3) does not provide shared locking, and requires that the
filehandle be open for writing (or appending, or read/writing).
.IP 3. 4
Some versions of \fBflock()\fR can't lock files over a network (e.g. on NFS file
systems), so you'd need to force the use of \fBfcntl\fR\|(2) when you build Perl.
But even this is dubious at best. See the flock entry of perlfunc
and the \fIINSTALL\fR file in the source distribution for information on
building Perl to do this.
.Sp
Two potentially non-obvious but traditional flock semantics are that
it waits indefinitely until the lock is granted, and that its locks are
\&\fImerely advisory\fR. Such discretionary locks are more flexible, but
offer fewer guarantees. This means that files locked with \fBflock()\fR may
be modified by programs that do not also use \fBflock()\fR. Cars that stop
for red lights get on well with each other, but not with cars that don't
stop for red lights. See the perlport manpage, your port's specific
documentation, or your system-specific local manpages for details. It's
best to assume traditional behavior if you're writing portable programs.
(If you're not, you should as always feel perfectly free to write
for your own system's idiosyncrasies (sometimes called "features").
Slavish adherence to portability concerns shouldn't get in the way of
your getting your job done.)
.Sp
For more information on file locking, see also
"File Locking" in perlopentut if you have it (new for 5.6).
.SS "Why can't I just open(FH, "">file.lock"")?"
.IX Xref "lock, lockfile race condition"
.IX Subsection "Why can't I just open(FH, "">file.lock"")?"
A common bit of code \fBNOT TO USE\fR is this:
.PP
.Vb 2
\&    sleep(3) while \-e \*(Aqfile.lock\*(Aq;    # PLEASE DO NOT USE
\&    open my $lock, \*(Aq>\*(Aq, \*(Aqfile.lock\*(Aq; # THIS BROKEN CODE
.Ve
.PP
This is a classic race condition: you take two steps to do something
which must be done in one. That's why computer hardware provides an
atomic test-and-set instruction. In theory, this "ought" to work:
.PP
.Vb 2
\&    sysopen my $fh, "file.lock", O_WRONLY|O_EXCL|O_CREAT
\&        or die "can\*(Aqt open  file.lock: $!";
.Ve
.PP
except that lamentably, file creation (and deletion) is not atomic
over NFS, so this won't work (at least, not every time) over the net.
Various schemes involving \fBlink()\fR have been suggested, but
these tend to involve busy-wait, which is also less than desirable.
.SS "I still don't get locking. I just want to increment the number in the file. How can I do this?"
.IX Xref "counter file, counter"
.IX Subsection "I still don't get locking. I just want to increment the number in the file. How can I do this?"
Didn't anyone ever tell you web-page hit counters were useless?
They don't count number of hits, they're a waste of time, and they serve
only to stroke the writer's vanity. It's better to pick a random number;
they're more realistic.
.PP
Anyway, this is what you can do if you can't help yourself.
.PP
.Vb 8
\&    use Fcntl qw(:DEFAULT :flock);
\&    sysopen my $fh, "numfile", O_RDWR|O_CREAT or die "can\*(Aqt open numfile: $!";
\&    flock $fh, LOCK_EX                        or die "can\*(Aqt flock numfile: $!";
\&    my $num = <$fh> || 0;
\&    seek $fh, 0, 0                            or die "can\*(Aqt rewind numfile: $!";
\&    truncate $fh, 0                           or die "can\*(Aqt truncate numfile: $!";
\&    (print $fh $num+1, "\en")                  or die "can\*(Aqt write numfile: $!";
\&    close $fh                                 or die "can\*(Aqt close numfile: $!";
.Ve
.PP
Here's a much better web-page hit counter:
.PP
.Vb 1
\&    $hits = int( (time() \- 850_000_000) / rand(1_000) );
.Ve
.PP
If the count doesn't impress your friends, then the code might. :\-)
.SS "All I want to do is append a small amount of text to the end of a file. Do I still have to use locking?"
.IX Xref "append file, append"
.IX Subsection "All I want to do is append a small amount of text to the end of a file. Do I still have to use locking?"
If you are on a system that correctly implements \f(CW\*(C`flock\*(C'\fR and you use
the example appending code from "perldoc \-f flock" everything will be
OK even if the OS you are on doesn't implement append mode correctly
(if such a system exists). So if you are happy to restrict yourself to
OSs that implement \f(CW\*(C`flock\*(C'\fR (and that's not really much of a
restriction) then that is what you should do.
.PP
If you know you are only going to use a system that does correctly
implement appending (i.e. not Win32) then you can omit the \f(CW\*(C`seek\*(C'\fR
from the code in the previous answer.
.PP
If you know you are only writing code to run on an OS and filesystem
that does implement append mode correctly (a local filesystem on a
modern Unix for example), and you keep the file in block-buffered mode
and you write less than one buffer-full of output between each manual
flushing of the buffer then each bufferload is almost guaranteed to be
written to the end of the file in one chunk without getting
intermingled with anyone else's output. You can also use the
\&\f(CW\*(C`syswrite\*(C'\fR function which is simply a wrapper around your system's
\&\f(CWwrite(2)\fR system call.
.PP
There is still a small theoretical chance that a signal will interrupt
the system-level \f(CWwrite()\fR operation before completion. There is also
a possibility that some STDIO implementations may call multiple system
level \f(CWwrite()\fRs even if the buffer was empty to start. There may be
some systems where this probability is reduced to zero, and this is
not a concern when using \f(CW\*(C`:perlio\*(C'\fR instead of your system's STDIO.
.SS "How do I randomly update a binary file?"
.IX Xref "file, binary patch"
.IX Subsection "How do I randomly update a binary file?"
If you're just trying to patch a binary, in many cases something as
simple as this works:
.PP
.Vb 1
\&    perl \-i \-pe \*(Aqs{window manager}{window mangler}g\*(Aq /usr/bin/emacs
.Ve
.PP
However, if you have fixed sized records, then you might do something more
like this:
.PP
.Vb 9
\&    my $RECSIZE = 220; # size of record, in bytes
\&    my $recno   = 37;  # which record to update
\&    open my $fh, \*(Aq+<\*(Aq, \*(Aqsomewhere\*(Aq or die "can\*(Aqt update somewhere: $!";
\&    seek $fh, $recno * $RECSIZE, 0;
\&    read $fh, $record, $RECSIZE == $RECSIZE or die "can\*(Aqt read record $recno: $!";
\&    # munge the record
\&    seek $fh, \-$RECSIZE, 1;
\&    print $fh $record;
\&    close $fh;
.Ve
.PP
Locking and error checking are left as an exercise for the reader.
Don't forget them or you'll be quite sorry.
.SS "How do I get a file's timestamp in perl?"
.IX Xref "timestamp file, timestamp"
.IX Subsection "How do I get a file's timestamp in perl?"
If you want to retrieve the time at which the file was last read,
written, or had its meta-data (owner, etc) changed, you use the \fB\-A\fR,
\&\fB\-M\fR, or \fB\-C\fR file test operations as documented in perlfunc.
These retrieve the age of the file (measured against the start-time of
your program) in days as a floating point number. Some platforms may
not have all of these times. See perlport for details. To retrieve
the "raw" time in seconds since the epoch, you would call the stat
function, then use \f(CWlocaltime()\fR, \f(CWgmtime()\fR, or
\&\f(CWPOSIX::strftime()\fR to convert this into human-readable form.
.PP
Here's an example:
.PP
.Vb 3
\&    my $write_secs = (stat($file))[9];
\&    printf "file %s updated at %s\en", $file,
\&        scalar localtime($write_secs);
.Ve
.PP
If you prefer something more legible, use the File::stat module
(part of the standard distribution in version 5.004 and later):
.PP
.Vb 5
\&    # error checking left as an exercise for reader.
\&    use File::stat;
\&    use Time::localtime;
\&    my $date_string = ctime(stat($file)\->mtime);
\&    print "file $file updated at $date_string\en";
.Ve
.PP
The \fBPOSIX::strftime()\fR approach has the benefit of being,
in theory, independent of the current locale. See perllocale
for details.
.SS "How do I set a file's timestamp in perl?"
.IX Xref "timestamp file, timestamp"
.IX Subsection "How do I set a file's timestamp in perl?"
You use the \fButime()\fR function documented in "utime" in perlfunc.
By way of example, here's a little program that copies the
read and write times from its first argument to all the rest
of them.
.PP
.Vb 6
\&    if (@ARGV < 2) {
\&        die "usage: cptimes timestamp_file other_files ...\en";
\&    }
\&    my $timestamp = shift;
\&    my($atime, $mtime) = (stat($timestamp))[8,9];
\&    utime $atime, $mtime, @ARGV;
.Ve
.PP
Error checking is, as usual, left as an exercise for the reader.
.PP
The perldoc for utime also has an example that has the same
effect as \fBtouch\fR\|(1) on files that \fIalready exist\fR.
.PP
Certain file systems have a limited ability to store the times
on a file at the expected level of precision. For example, the
FAT and HPFS filesystem are unable to create dates on files with
a finer granularity than two seconds. This is a limitation of
the filesystems, not of \fButime()\fR.
.SS "How do I print to more than one file at once?"
.IX Xref "print, to multiple files"
.IX Subsection "How do I print to more than one file at once?"
To connect one filehandle to several output filehandles,
you can use the IO::Tee or Tie::FileHandle::Multiplex modules.
.PP
If you only have to do this once, you can print individually
to each filehandle.
.PP
.Vb 1
\&    for my $fh ($fh1, $fh2, $fh3) { print $fh "whatever\en" }
.Ve
.SS "How can I read in an entire file all at once?"
.IX Xref "slurp file, slurping"
.IX Subsection "How can I read in an entire file all at once?"
The customary Perl approach for processing all the lines in a file is to
do so one line at a time:
.PP
.Vb 6
\&    open my $input, \*(Aq<\*(Aq, $file or die "can\*(Aqt open $file: $!";
\&    while (<$input>) {
\&        chomp;
\&        # do something with $_
\&    }
\&    close $input or die "can\*(Aqt close $file: $!";
.Ve
.PP
This is tremendously more efficient than reading the entire file into
memory as an array of lines and then processing it one element at a time,
which is often\-\-if not almost always\-\-the wrong approach. Whenever
you see someone do this:
.PP
.Vb 1
\&    my @lines = <INPUT>;
.Ve
.PP
You should think long and hard about why you need everything loaded at
once. It's just not a scalable solution.
.PP
If you "mmap" the file with the File::Map module from
CPAN, you can virtually load the entire file into a
string without actually storing it in memory:
.PP
.Vb 1
\&    use File::Map qw(map_file);
\&
\&    map_file my $string, $filename;
.Ve
.PP
Once mapped, you can treat \f(CW$string\fR as you would any other string.
Since you don't necessarily have to load the data, mmap-ing can be
very fast and may not increase your memory footprint.
.PP
You might also find it more
fun to use the standard Tie::File module, or the DB_File module's
\&\f(CW$DB_RECNO\fR bindings, which allow you to tie an array to a file so that
accessing an element of the array actually accesses the corresponding
line in the file.
.PP
If you want to load the entire file, you can use the Path::Tiny
module to do it in one simple and efficient step:
.PP
.Vb 1
\&    use Path::Tiny;
\&
\&    my $all_of_it = path($filename)\->slurp; # entire file in scalar
\&    my @all_lines = path($filename)\->lines; # one line per element
.Ve
.PP
Or you can read the entire file contents into a scalar like this:
.PP
.Vb 6
\&    my $var;
\&    {
\&        local $/;
\&        open my $fh, \*(Aq<\*(Aq, $file or die "can\*(Aqt open $file: $!";
\&        $var = <$fh>;
\&    }
.Ve
.PP
That temporarily undefs your record separator, and will automatically
close the file at block exit. If the file is already open, just use this:
.PP
.Vb 1
\&    my $var = do { local $/; <$fh> };
.Ve
.PP
You can also use a localized \f(CW@ARGV\fR to eliminate the \f(CW\*(C`open\*(C'\fR:
.PP
.Vb 1
\&    my $var = do { local( @ARGV, $/ ) = $file; <> };
.Ve
.SS "How can I read in a file by paragraphs?"
.IX Xref "file, reading by paragraphs"
.IX Subsection "How can I read in a file by paragraphs?"
Use the \f(CW$/\fR variable (see perlvar for details). You can either
set it to \f(CW""\fR to eliminate empty paragraphs (\f(CW"abc\en\en\en\endef"\fR,
for instance, gets treated as two paragraphs and not three), or
\&\f(CW"\en\en"\fR to accept empty paragraphs.
.PP
Note that a blank line must have no blanks in it. Thus
\&\f(CW"fred\en\ \enstuff\en\en"\fR is one paragraph, but \f(CW"fred\en\enstuff\en\en"\fR is two.
.SS "How can I read a single character from a file? From the keyboard?"
.IX Xref "getc file, reading one character at a time"
.IX Subsection "How can I read a single character from a file? From the keyboard?"
You can use the builtin \f(CWgetc()\fR function for most filehandles, but
it won't (easily) work on a terminal device. For STDIN, either use
the Term::ReadKey module from CPAN or use the sample code in
"getc" in perlfunc.
.PP
If your system supports the portable operating system programming
interface (POSIX), you can use the following code, which you'll note
turns off echo processing as well.
.PP
.Vb 9
\&    #!/usr/bin/perl \-w
\&    use strict;
\&    $| = 1;
\&    for (1..4) {
\&        print "gimme: ";
\&        my $got = getone();
\&        print "\-\-> $got\en";
\&    }
\&    exit;
\&
\&    BEGIN {
\&        use POSIX qw(:termios_h);
\&
\&        my ($term, $oterm, $echo, $noecho, $fd_stdin);
\&
\&        my $fd_stdin = fileno(STDIN);
\&
\&        $term     = POSIX::Termios\->new();
\&        $term\->getattr($fd_stdin);
\&        $oterm     = $term\->getlflag();
\&
\&        $echo     = ECHO | ECHOK | ICANON;
\&        $noecho   = $oterm & ~$echo;
\&
\&        sub cbreak {
\&            $term\->setlflag($noecho);
\&            $term\->setcc(VTIME, 1);
\&            $term\->setattr($fd_stdin, TCSANOW);
\&        }
\&
\&        sub cooked {
\&            $term\->setlflag($oterm);
\&            $term\->setcc(VTIME, 0);
\&            $term\->setattr($fd_stdin, TCSANOW);
\&        }
\&
\&        sub getone {
\&            my $key = \*(Aq\*(Aq;
\&            cbreak();
\&            sysread(STDIN, $key, 1);
\&            cooked();
\&            return $key;
\&        }
\&    }
\&
\&    END { cooked() }
.Ve
.PP
The Term::ReadKey module from CPAN may be easier to use. Recent versions
include also support for non-portable systems as well.
.PP
.Vb 8
\&    use Term::ReadKey;
\&    open my $tty, \*(Aq<\*(Aq, \*(Aq/dev/tty\*(Aq;
\&    print "Gimme a char: ";
\&    ReadMode "raw";
\&    my $key = ReadKey 0, $tty;
\&    ReadMode "normal";
\&    printf "\enYou said %s, char number %03d\en",
\&        $key, ord $key;
.Ve
.SS "How can I tell whether there's a character waiting on a filehandle?"
.IX Subsection "How can I tell whether there's a character waiting on a filehandle?"
The very first thing you should do is look into getting the Term::ReadKey
extension from CPAN. As we mentioned earlier, it now even has limited
support for non-portable (read: not open systems, closed, proprietary,
not POSIX, not Unix, etc.) systems.
.PP
You should also check out the Frequently Asked Questions list in
comp.unix.* for things like this: the answer is essentially the same.
It's very system-dependent. Here's one solution that works on BSD
systems:
.PP
.Vb 5
\&    sub key_ready {
\&        my($rin, $nfd);
\&        vec($rin, fileno(STDIN), 1) = 1;
\&        return $nfd = select($rin,undef,undef,0);
\&    }
.Ve
.PP
If you want to find out how many characters are waiting, there's
also the FIONREAD ioctl call to be looked at. The \fIh2ph\fR tool that
comes with Perl tries to convert C include files to Perl code, which
can be \f(CW\*(C`require\*(C'\fRd. FIONREAD ends up defined as a function in the
\&\fIsys/ioctl.ph\fR file:
.PP
.Vb 1
\&    require \*(Aq./sys/ioctl.ph\*(Aq;
\&
\&    $size = pack("L", 0);
\&    ioctl(FH, FIONREAD(), $size)    or die "Couldn\*(Aqt call ioctl: $!\en";
\&    $size = unpack("L", $size);
.Ve
.PP
If \fIh2ph\fR wasn't installed or doesn't work for you, you can
\&\fIgrep\fR the include files by hand:
.PP
.Vb 2
\&    % grep FIONREAD /usr/include/*/*
\&    /usr/include/asm/ioctls.h:#define FIONREAD      0x541B
.Ve
.PP
Or write a small C program using the editor of champions:
.PP
.Vb 9
\&    % cat > fionread.c
\&    #include <sys/ioctl.h>
\&    main() {
\&        printf("%#08x\en", FIONREAD);
\&    }
\&    ^D
\&    % cc \-o fionread fionread.c
\&    % ./fionread
\&    0x4004667f
.Ve
.PP
And then hard-code it, leaving porting as an exercise to your successor.
.PP
.Vb 1
\&    $FIONREAD = 0x4004667f;         # XXX: opsys dependent
\&
\&    $size = pack("L", 0);
\&    ioctl(FH, $FIONREAD, $size)     or die "Couldn\*(Aqt call ioctl: $!\en";
\&    $size = unpack("L", $size);
.Ve
.PP
FIONREAD requires a filehandle connected to a stream, meaning that sockets,
pipes, and tty devices work, but \fInot\fR files.
.ie n .SS "How do I do a ""tail \-f"" in perl?"
.el .SS "How do I do a \f(CWtail \-f\fP in perl?"
.IX Xref "tail IO::Handle File::Tail clearerr"
.IX Subsection "How do I do a tail -f in perl?"
First try
.PP
.Vb 1
\&    seek($gw_fh, 0, 1);
.Ve
.PP
The statement \f(CW\*(C`seek($gw_fh, 0, 1)\*(C'\fR doesn't change the current position,
but it does clear the end-of-file condition on the handle, so that the
next \f(CW\*(C`<$gw_fh>\*(C'\fR makes Perl try again to read something.
.PP
If that doesn't work (it relies on features of your stdio implementation),
then you need something more like this:
.PP
.Vb 7
\&    for (;;) {
\&      for ($curpos = tell($gw_fh); <$gw_fh>; $curpos =tell($gw_fh)) {
\&        # search for some stuff and put it into files
\&      }
\&      # sleep for a while
\&      seek($gw_fh, $curpos, 0);  # seek to where we had been
\&    }
.Ve
.PP
If this still doesn't work, look into the \f(CW\*(C`clearerr\*(C'\fR method
from IO::Handle, which resets the error and end-of-file states
on the handle.
.PP
There's also a File::Tail module from CPAN.
.SS "How do I \fBdup()\fP a filehandle in Perl?"
.IX Xref "dup"
.IX Subsection "How do I dup() a filehandle in Perl?"
If you check "open" in perlfunc, you'll see that several of the ways
to call \fBopen()\fR should do the trick. For example:
.PP
.Vb 2
\&    open my $log, \*(Aq>>\*(Aq, \*(Aq/foo/logfile\*(Aq;
\&    open STDERR, \*(Aq>&\*(Aq, $log;
.Ve
.PP
Or even with a literal numeric descriptor:
.PP
.Vb 2
\&    my $fd = $ENV{MHCONTEXTFD};
\&    open $mhcontext, "<&=$fd";  # like fdopen(3S)
.Ve
.PP
Note that "<&STDIN" makes a copy, but "<&=STDIN" makes
an alias. That means if you close an aliased handle, all
aliases become inaccessible. This is not true with
a copied one.
.PP
Error checking, as always, has been left as an exercise for the reader.
.SS "How do I close a file descriptor by number?"
.IX Xref "file, closing file descriptors POSIX close"
.IX Subsection "How do I close a file descriptor by number?"
If, for some reason, you have a file descriptor instead of a
filehandle (perhaps you used \f(CW\*(C`POSIX::open\*(C'\fR), you can use the
\&\f(CWclose()\fR function from the POSIX module:
.PP
.Vb 1
\&    use POSIX ();
\&
\&    POSIX::close( $fd );
.Ve
.PP
This should rarely be necessary, as the Perl \f(CWclose()\fR function is to be
used for things that Perl opened itself, even if it was a dup of a
numeric descriptor as with \f(CW\*(C`MHCONTEXT\*(C'\fR above. But if you really have
to, you may be able to do this:
.PP
.Vb 3
\&    require \*(Aq./sys/syscall.ph\*(Aq;
\&    my $rc = syscall(SYS_close(), $fd + 0);  # must force numeric
\&    die "can\*(Aqt sysclose $fd: $!" unless $rc == \-1;
.Ve
.PP
Or, just use the fdopen(3S) feature of \f(CWopen()\fR:
.PP
.Vb 4
\&    {
\&        open my $fh, "<&=$fd" or die "Cannot reopen fd=$fd: $!";
\&        close $fh;
\&    }
.Ve
.SS "Why can't I use ""C:\etemp\efoo"" in DOS paths? Why doesn't `C:\etemp\efoo.exe` work?"
.IX Xref "filename, DOS issues"
.IX Subsection "Why can't I use ""C:tempfoo"" in DOS paths? Why doesn't `C:tempfoo.exe` work?"
Whoops!  You just put a tab and a formfeed into that filename!
Remember that within double quoted strings ("like\ethis"), the
backslash is an escape character. The full list of these is in
"Quote and Quote-like Operators" in perlop. Unsurprisingly, you don't
have a file called "c:(tab)emp(formfeed)oo" or
"c:(tab)emp(formfeed)oo.exe" on your legacy DOS filesystem.
.PP
Either single-quote your strings, or (preferably) use forward slashes.
Since all DOS and Windows versions since something like MS-DOS 2.0 or so
have treated \f(CW\*(C`/\*(C'\fR and \f(CW\*(C`\e\*(C'\fR the same in a path, you might as well use the
one that doesn't clash with Perl\-\-or the POSIX shell, ANSI C and C++,
awk, Tcl, Java, or Python, just to mention a few. POSIX paths
are more portable, too.
.SS "Why doesn't glob(""*.*"") get all the files?"
.IX Xref "glob"
.IX Subsection "Why doesn't glob(""*.*"") get all the files?"
Because even on non-Unix ports, Perl's glob function follows standard
Unix globbing semantics. You'll need \f(CWglob("*")\fR to get all (non-hidden)
files. This makes \fBglob()\fR portable even to legacy systems. Your
port may include proprietary globbing functions as well. Check its
documentation for details.
.ie n .SS "Why does Perl let me delete read-only files? Why does ""\-i"" clobber protected files? Isn't this a bug in Perl?"
.el .SS "Why does Perl let me delete read-only files? Why does \f(CW\-i\fP clobber protected files? Isn't this a bug in Perl?"
.IX Subsection "Why does Perl let me delete read-only files? Why does -i clobber protected files? Isn't this a bug in Perl?"
This is elaborately and painstakingly described in the
\&\fIfile-dir-perms\fR article in the "Far More Than You Ever Wanted To
Know" collection in <http://www.cpan.org/misc/olddoc/FMTEYEWTK.tgz> .
.PP
The executive summary: learn how your filesystem works. The
permissions on a file say what can happen to the data in that file.
The permissions on a directory say what can happen to the list of
files in that directory. If you delete a file, you're removing its
name from the directory (so the operation depends on the permissions
of the directory, not of the file). If you try to write to the file,
the permissions of the file govern whether you're allowed to.
.SS "How do I select a random line from a file?"
.IX Xref "file, selecting a random line"
.IX Subsection "How do I select a random line from a file?"
Short of loading the file into a database or pre-indexing the lines in
the file, there are a couple of things that you can do.
.PP
Here's a reservoir-sampling algorithm from the Camel Book:
.PP
.Vb 2
\&    srand;
\&    rand($.) < 1 && ($line = $_) while <>;
.Ve
.PP
This has a significant advantage in space over reading the whole file
in. You can find a proof of this method in \fIThe Art of Computer
Programming\fR, Volume 2, Section 3.4.2, by Donald E. Knuth.
.PP
You can use the File::Random module which provides a function
for that algorithm:
.PP
.Vb 2
\&    use File::Random qw/random_line/;
\&    my $line = random_line($filename);
.Ve
.PP
Another way is to use the Tie::File module, which treats the entire
file as an array. Simply access a random array element.
.SS "Why do I get weird spaces when I print an array of lines?"
.IX Subsection "Why do I get weird spaces when I print an array of lines?"
(contributed by brian d foy)
.PP
If you are seeing spaces between the elements of your array when
you print the array, you are probably interpolating the array in
double quotes:
.PP
.Vb 2
\&    my @animals = qw(camel llama alpaca vicuna);
\&    print "animals are: @animals\en";
.Ve
.PP
It's the double quotes, not the \f(CW\*(C`print\*(C'\fR, doing this. Whenever you
interpolate an array in a double quote context, Perl joins the
elements with spaces (or whatever is in \f(CW$"\fR, which is a space by
default):
.PP
.Vb 1
\&    animals are: camel llama alpaca vicuna
.Ve
.PP
This is different than printing the array without the interpolation:
.PP
.Vb 2
\&    my @animals = qw(camel llama alpaca vicuna);
\&    print "animals are: ", @animals, "\en";
.Ve
.PP
Now the output doesn't have the spaces between the elements because
the elements of \f(CW@animals\fR simply become part of the list to
\&\f(CW\*(C`print\*(C'\fR:
.PP
.Vb 1
\&    animals are: camelllamaalpacavicuna
.Ve
.PP
You might notice this when each of the elements of \f(CW@array\fR end with
a newline. You expect to print one element per line, but notice that
every line after the first is indented:
.PP
.Vb 3
\&    this is a line
\&     this is another line
\&     this is the third line
.Ve
.PP
That extra space comes from the interpolation of the array. If you
don't want to put anything between your array elements, don't use the
array in double quotes. You can send it to print without them:
.PP
.Vb 1
\&    print @lines;
.Ve
.SS "How do I traverse a directory tree?"
.IX Subsection "How do I traverse a directory tree?"
(contributed by brian d foy)
.PP
The File::Find module, which comes with Perl, does all of the hard
work to traverse a directory structure. It comes with Perl. You simply
call the \f(CW\*(C`find\*(C'\fR subroutine with a callback subroutine and the
directories you want to traverse:
.PP
.Vb 1
\&    use File::Find;
\&
\&    find( \e&wanted, @directories );
\&
\&    sub wanted {
\&        # full path in $File::Find::name
\&        # just filename in $_
\&        ... do whatever you want to do ...
\&    }
.Ve
.PP
The File::Find::Closures, which you can download from CPAN, provides
many ready-to-use subroutines that you can use with File::Find.
.PP
The File::Finder, which you can download from CPAN, can help you
create the callback subroutine using something closer to the syntax of
the \f(CW\*(C`find\*(C'\fR command-line utility:
.PP
.Vb 2
\&    use File::Find;
\&    use File::Finder;
\&
\&    my $deep_dirs = File::Finder\->depth\->type(\*(Aqd\*(Aq)\->ls\->exec(\*(Aqrmdir\*(Aq,\*(Aq{}\*(Aq);
\&
\&    find( $deep_dirs\->as_options, @places );
.Ve
.PP
The File::Find::Rule module, which you can download from CPAN, has
a similar interface, but does the traversal for you too:
.PP
.Vb 1
\&    use File::Find::Rule;
\&
\&    my @files = File::Find::Rule\->file()
\&                             \->name( \*(Aq*.pm\*(Aq )
\&                             \->in( @INC );
.Ve
.SS "How do I delete a directory tree?"
.IX Subsection "How do I delete a directory tree?"
(contributed by brian d foy)
.PP
If you have an empty directory, you can use Perl's built-in \f(CW\*(C`rmdir\*(C'\fR.
If the directory is not empty (so, with files or subdirectories), you
either have to empty it yourself (a lot of work) or use a module to
help you.
.PP
The File::Path module, which comes with Perl, has a \f(CW\*(C`remove_tree\*(C'\fR
which can take care of all of the hard work for you:
.PP
.Vb 1
\&    use File::Path qw(remove_tree);
\&
\&    remove_tree( @directories );
.Ve
.PP
The File::Path module also has a legacy interface to the older
\&\f(CW\*(C`rmtree\*(C'\fR subroutine.
.SS "How do I copy an entire directory?"
.IX Subsection "How do I copy an entire directory?"
(contributed by Shlomi Fish)
.PP
To do the equivalent of \f(CW\*(C`cp \-R\*(C'\fR (i.e. copy an entire directory tree
recursively) in portable Perl, you'll either need to write something yourself
or find a good CPAN module such as  File::Copy::Recursive.
.SH "AUTHOR AND COPYRIGHT"
.IX Header "AUTHOR AND COPYRIGHT"
Copyright (c) 1997\-2010 Tom Christiansen, Nathan Torkington, and
other authors as noted. All rights reserved.
.PP
This documentation is free; you can redistribute it and/or modify it
under the same terms as Perl itself.
.PP
Irrespective of its distribution, all code examples here are in the public
domain. You are permitted and encouraged to use this code and any
derivatives thereof in your own programs for fun or for profit as you
see fit. A simple comment in the code giving credit to the FAQ would
be courteous but is not required.