This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Configure patch for vfork et al on VMS


On Dec  7, 2001, "Douglas B. Rupp" <rupp@gnat.com> wrote:

>> Then please arrange to have the initial length of the string computed,
>> and double it with the command above on every loop iteration, instead
>> of re-computing the length of the string.

> I don't see how this will show the actual length of the command line that is accepted.

The `test' command right before the assignment would fail should we
exceed the limit.

> I think we are better off hardcoding the value.

Hardcoding goes against the autoconf-recommended practice of testing
for features, not for OSs.  What if the next version of VMS (heh :-)
changes these limits?  Are we going to have to modify the scripts
then?  What about scripts already shipped?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]