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:
Run that and “a” will be displayed. That was easy enough. Now the command line way:
Now the magic angle bracket way:
If you want, you can do things when each file ends:
And of course you can accumulate all the lines instead:
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:
(I’m making this code artificially simple. This works, but isn’t the way you would probably do it in reality.)
0
0
0
hello
1
0 hello
0
0
0
0
0
hello
1
1 This is A
1
0 hello
0
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:
The angle brackets have one more trick up their sleeves:
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.
A.P. Lawrence provides SCO Unix and Linux consulting services http://www.pcunix.com
