home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.perl
- Path: sparky!uunet!ftpbox!mothost!merlin.dev.cdx.mot.com!fendahl.dev.cdx.mot.com!mcook
- From: mcook@fendahl.dev.cdx.mot.com (Michael Cook)
- Subject: Re: Is this a perl bug?
- Message-ID: <mcook.724207619@fendahl.dev.cdx.mot.com>
- Sender: news@merlin.dev.cdx.mot.com (USENET News System)
- Nntp-Posting-Host: fendahl.dev.cdx.mot.com
- Organization: Motorola Codex, Canton, Massachusetts
- References: <1992Dec6.232905.13545@reed.edu> <1992Dec8.175616.20198@netlabs.com> <9212111642.AA27958@brimstone.unipalm.co.uk> <1992Dec12.072651.653@netlabs.com>
- Date: Sun, 13 Dec 1992 00:46:59 GMT
- Lines: 16
-
- lwall@netlabs.com (Larry Wall) writes:
-
- >Similarly, `cat $foo` turns into something like backtick('cat ' . $foo),
- >though I haven't actually put in a keyword to access that function yet.
-
- Cool. Would we be able to do something like this: backtick('cat',$foo), which
- would be analogous to system('cat',$foo) vs. system("cat $foo")?
-
- And how about having it so the file name in open() can be separated from the
- directive characters: open(FH,">",$foo). That way, it would still work even
- if the file name had funny characters (such as leading/trailing whitespace).
-
- And open(FH,"|-",'cat',$foo) could be like open(FH,"|cat $foo"), except that
- it would be done directly via exec, not via "sh -c".
-
- Michael.
-