Message-ID: <380F5677.996ED35F@softhome.net>
Date: Thu, 21 Oct 1999 20:07:51 +0200
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: lt,en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Help with arg passing
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990930133520 DOT 20873I-100000 AT is>
Content-Type: text/plain; charset=iso-8859-4
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> The missing piece in this puzzle is that the !proxy method is used by
> `system' only if the command line is longer than the DOS limit;
> otherwise, the child program is invoked as non-DJGPP programs would,
> with all its command-line arguments passed via the DOS call.  (The
> reason for this is my own conservatism in the face of all the
> subtleties that go on in system.c, dosexec.c, and c1args.c: when I did
> the change that enabled long command lines in `system', I wanted to
> minimize any adverse effects of some subtle misfeature that could be
> lurking somewhere.)

After some pause, I'm continuing symlink development. Because I want
to see my patch in libc sources, I have a question regarding above:
is it acceptable to turn on !proxy method for calling all DJGPP programs
in 2.04 ? If I understand correctly, the main reason not to do so was
"some subtle misfeature that could be lurking somewhere". But most GNU
makefiles anyway use long command lines, so can't we assume that this
feature is well tested now ? If we don't do this, program called via
symlink will see symlink's name only if it has long command line too.

Laurynas Biveinis