(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Kerio Reseller
Printer Friendly Version

Perl Input

Perl has wonderful I/O capabilities. I'm only going to cover input here: reading from files or standard input. There are two ways to do that (actually a lot more than two, but this is supposed to be introductory material): you can open a specific file, or you can pass files on the command line and either open them individually or just ignore the whole thing and pretend everything is coming from STDIN.

Let's just take a look at some simple examples. Create files a, b and c with text you will recognize, and try this:


Hate these ads?



#!/usr/bin/perl
open(F,"a");
while (<F>) {
  print;
}


Run that and "a" will be displayed. That was easy enough. Now the command line way:



#!/usr/bin/perl
foreach (@ARGV) {
  open(F,$_);
  while (<F>) {
    print;
  }
}


If you called that t.pl, run ./t.pl a b c and you'll see each of your files go by. Notice that I didn't bother to close F. There are cases where being sloppy like that could get you in trouble, but in this simple situation, Perl happily closes the previous file for you when it sees you re-using F.

Now the magic angle bracket way:



#!/usr/bin/perl
while (<>) {
 print;
}







Try that both by itself (type lines to it), and as ./t.pl a b c, and finally as cat a b c | ./t.pl. You'll see that whatever you do, it reads the lines or the files. When you give it file names, they act like they came from STDIN. If you don't, it reads STDIN. If you want to read BOTH the files and STDIN, do ./t.pl a b c -.

If you want, you can do things when each file ends:



#!/usr/bin/perl
while (<>) {
 print;
 print "--- End of $ARGV ----\n" if eof;
}


And of course you can accumulate all the lines instead:



#!/usr/bin/perl
@lines=(<>) ;
.. do stuff
print @lines;


Now we're going to get much trickier. We're not going to read unless there is something ready to read. This can be useful if you need to do other things while waiting for input, or if you don't want lack of input to hold you up forever. The code will use Perl's "select" command, which just passes to the system level select() call. Perl's "select" is one of those overloaded functions that does very different things depending on how many arguments you give it, so don't get confused here. This is the usage that tells us whether or not filehandles are ready for io. We also use the "fileno" command to get the actual file number of STDIN. The "vec" is used to turn "$rin" into a bit structure that is what the system level select() is looking for; if STDIN is file number 0 as it would be if not redirected, then the first bit of $rin get sets to 1 before we call the Perl select (you don't have to understand that to use it). The structure gets changed by select(), so we protect it with the "$rout=$rin"; $rout will get changed, not $rin. It all sounds very complicated, but it really isn't bad in usage:



#!/usr/bin/perl
$rin="";
vec($rin,fileno(STDIN),1)=1;
while (1) {
sleep 2;
$nfound=select($rout=$rin,"","",1);
print "$nfound $what\n";
$what="";
$what=<>if ($nfound) ;
}


(I'm making this code artificially simple. This works, but isn't the way you would probably do it in reality.)

Try that first with just ./t.pl. You'll see it print 0 every two seconds. If you type something, it only gets read when you press enter (buffered input). Use CTRL-C or your INTR character to quit this.


M3IP inc.





hello

0 hello







Now try it like this: ./t.pl a. My "a" contains "This is A":






hello

1 This is A




0 hello






Nothing happened until we gave it a line on STDIN. Then, and only then, did Perl rearrange things so that the file "a" came through STDIN before our line. That makes sense, because until you try to read STDIN, Perl has no idea what your intentions toward the files on the command line are. You might want to process them specifically as we did in the second little script.

Single character input is a little trickier, because you first need to convince your OS that it should be feeding you that way. Exactly how you do that depends on the heritage of your system; it's going to be a "stty" command of some sort. This works on my Mac OS X box:



#!/usr/bin/perl
system "stty cbreak < /dev/tty > /dev/tty 2>&1";
while (($key=getc) ) {
  print "$key\n";
  last if $key eq "q";
};
system "stty -cbreak < /dev/tty > /dev/tty 2>&1";


The angle brackets have one more trick up their sleeves:



foreach (<[a-c]*;>) {
  open(F,$_);
  while (<F>) {
    print;
  }
}


That opens every file that begins with "a", "b' or "c". Use any wild card characters you need just like you would at the command line.

This should give you some feel for the flexibility of Perl input.



Comments /Unix/perlinput.html
PerlInput :hgfhfgh



Add your comments

Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)

Or use any RSS reader

Delivered by FeedBurner





Views for this page
Today This Week This Month This Year  Overall
644632313,064 79,617

numly esn 77893-080107-696068-48
n umly barcode

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

pavatar.jpg
More:
       - Perl
       - Programming
       - Code




Unix/Linux Consultants

Your ad here - $24.00 yearly!

http://www.breakthru.com.au SCO (Openserver and Unixware), Unix, Solaris and Linux Consulting services including: Secure Networking Solutions; Linux based Firewalls; Backup Solutions; Secure Home to Office Network Setup; Phone, Remote and On-Site Support available - Satisfaction Guaranteed!


SCO, OpenServer, UnixWare, software, servers, security, networks, installation, administration, troubleshooting, maintenance, Watchguard, firewalls, VPNs, e-mail. Visit us at http://opensystemscomputing.com and www.go2unix.com.


http://www.loch-raven.com/ Over 18 years of experience Unix and Linux servers. Linux and Unix consulting, system administration, remote administration, custom scripting, web desing and hosting.




Twitter
  • Jun 26 21:28
    Lost 5 cents at poker tonight. Hard to do with 10 and 20 cent betting..
  • Jun 23 07:01
    Hypermiling:




card_image






Coming Attractions

My Favorites

Change Congress

Related Posts