[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Improving maximum command line length detection (Was: Re: [PATCH] Re

From: Peter O'Gorman
Subject: Re: Improving maximum command line length detection (Was: Re: [PATCH] Removal of obsolete AmigaOS support)
Date: Wed, 08 Oct 2003 09:38:15 +0900
User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5b) Gecko/20030902 Thunderbird/0.2

Dalibor Topic wrote:
there were no replys on the ammended method. If anyone objects to me putting in an 8K test string into libtool's libtool.m4 please do it now, before I start learning m4 ;)

I object, mostly because I think you'll find that the time taken to do
testring=$testring$testring is insignificant compared to all the time spent doing string compares, getting the string length, exec'ing the script over etc.

If you want to start off with a bigger string then make it bigger in a loop. Something like:
for p in 3 4 5 6 7 8 9 10 11 12 13 ; do

And put that before the real testing max_cmd_length loop.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]