Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!littlei!omepd!merlyn
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.unix.questions
Subject: Re: cc -o *.c
Message-ID: <5199@omepd.UUCP>
Date: 16 Nov 89 00:49:40 GMT
Article-I.D.: omepd.5199
References: <297@cerc.wvu.wvnet.edu.edu> <20512@mimsy.umd.edu> <1042@root44.co.uk> <1989Nov9.145517.4338@virtech.uucp> <20619@unix.cis.pitt.edu>
Sender: news@omepd.UUCP
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Hillsboro, Oregon, USA
Lines: 41
In-reply-to: cmf@obie.cis.pitt.edu (Carl M. Fongheiser)

In article <20619@unix.cis.pitt.edu>, cmf@obie (Carl M. Fongheiser) writes:
| In article <1989Nov9.145517.4338@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes:
| ] In article <1042@root44.co.uk>, gwc@root.co.uk (Geoff Clare) writes:
| ] > In article <20512@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes:
| ] > >
| ] > >	% echo *.c
| ] > >	t.c tet.c t.c
| ] > 
| ] > That's a neat trick, Chris.  Care to tell us how you managed it?
| ] 
| ] easy,
| ] 
| ] 	% cp /dev/null t.c
| ] 	% cp /dev/null tet.c
| ] 	% cp /dev/null "tj\<BACKSPACE>.c "
| ] 	% echo *.c
| ] 	t.c tet.c t.c
| 
| Nah, even easier:
| 
| cp /dev/null 't.c tet.c t.c'
| 
| 			Carl Fongheiser
| 			cmf@unix.cis.pitt.edu

Why get /dev/null involved?  Or even exec a process?

$ >'t.c tet.c t.c'

:-)

OB Perl Reference:

perl -e 'open(STDOUT,">t.c tet.c t.c");'

Just another Perl heckler,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Hillsboro, Oregon, USA, Sol III  |
| merlyn@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn	         |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/