Xref: utzoo comp.lang.c:17367 comp.unix.wizards:15357
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdahl!nsc!taux01!orr
From: orr@taux01.UUCP (Orr Michael )
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: How to predict size of outcome of vsprintf?
Message-ID: <1411@taux01.UUCP>
Date: 3 Apr 89 07:37:48 GMT
References: <993@etnibsd.UUCP> <9872@smoke.BRL.MIL> <28831@bu-cs.BU.EDU> <1618@thor.acc.stolaf.edu> <9979@bloom-beacon.MIT.EDU> <1989Mar21.183741.1089@utzoo.uucp> <12135@haddock.ima.isc.com>
Reply-To: orr@taux01.UUCP (Orr Michael )
Organization: National Semiconductor (IC) Ltd, Israel
Lines: 17

In article <12135@haddock.ima.isc.com> 
   karl@haddock.ima.isc.com (Karl Heuer) writes:
>
>But `msprintf' has the flaw that the va_list version would be named
>`vmsprintf', which suggests that it has something to do with a certain
>obscure operating system.
>
>Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint
 ... In which 'printf' itself is limited to 512 chars at most, getting you
a crash if you try printing longer strings ...


-- 
orr@nsc			  	      IBM's motto: Machines should work,
{amdahl,decwrl,hplabs,pyramid,sun}!nsc!orr         People should think.
                                 	      Orr's remark: Neither do.
Disclaimer: Opinions, come home. All is forgiven. Papa.