Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!shelby!rutgers!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.perl
Subject: Re: -T and named pipes
Message-ID: <25787:Feb2000:18:4991@kramden.acf.nyu.edu>
Date: 20 Feb 91 00:18:49 GMT
References: <11483@jpl-devvax.JPL.NASA.GOV> <527@rufus.UUCP> <11485@jpl-devvax.JPL.NASA.GOV>
Organization: IR
Lines: 13

In article <11485@jpl-devvax.JPL.NASA.GOV> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes:
> I suspect that FIFOs should ordinarily be banned from ordinary directories.
> Perl is not the only program that will have such difficulties.

There aren't many programs that try to intuit what a file is from its
contents unless they plan to make some use of those contents. The
``file'' program is a counterexample, and at least Sun's ``file''
detects and reports fifos properly. I assume the same is true under
straight System V.

What other programs are you thinking of?

---Dan