-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Reid Madsen
Sent: Monday, November 06, 2000 5:42 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: GNU enhancement -- $(xargs cmd, list)
Date: 6 Nov 2000 16:56:30 -0600
%% Reid Madsen [EMAIL PROTECTED] writes:
rm Consider the following:
rm ARGS=$(wildcard *.xx)
rm target:
rm command $(ARGS)
rm The above only works if the length of the resulting command line
rm is within system limits. From the shell, you can solve this by:
rm
Your xargs feature sounds useful, but your bug example is flawed. Remember
that the
shell does all wildcard expansion in Unix. For most problem cases, your
echo *.xx | xargs command
commandline would fail for the same reason that
command *.xx
would fail. Just wanted to make sure the actual
Date: Mon, 6 Nov 2000 10:54:13 -0500
From: "Paul D. Smith" [EMAIL PROTECTED]
This can't work; remember that make passes each line whole to a
subshell. If the line is too long for any individual shell invocation,
then chopping it up and sending it to one subshell will certainly be
Well, I've got a prototype up and running and IMHO it's quite cool.
All changes are in function.c. The net of the changes are:
* Added support for:
$(xargs command, list)
which is expanded to:
cat tmpfile | xargs command; rm -f tmpfile
* Added 'func_xargs' as shown
lto:[EMAIL PROTECTED]]On Behalf Of
Reid Madsen
Sent: Monday, November 06, 2000 12:29 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: GNU enhancement -- $(xargs cmd, list)
Well, I've got a prototype up and running and IMHO it's quite cool.
All changes are in function.c. Th
Date: 6 Nov 2000 16:56:30 -0600
From: Reid Madsen [EMAIL PROTECTED]
I also thought about using the _POSIX_ARG_MAX and ARG_MAX symbols to determine
when the xargs approach was really needed. If the command line is within
limits, then
$(xargs cmd, list)
would expand
