Xref: utzoo comp.lang.c:17120 comp.unix.wizards:15164
Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!decwrl!decvax!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: How to predict size of outcome of vsprintf?
Message-ID: <12135@haddock.ima.isc.com>
Date: 23 Mar 89 01:58:44 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>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 13

In <1989Mar21.183741.1089@utzoo.uucp> henry@utzoo (Henry Spencer) writes:
>In <9979@bloom-beacon.MIT.EDU> scs@adam.pika.mit.edu (Steve Summit) writes:
>>My own soon-to-be-released stdio replacement contains
>>	char *smprintf(char *fmt, ...)
>
>I would urge changing the name, perhaps to msprintf, to avoid a name that
>looks very similar to snprintf at first glance.

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.  I think I'd go with `mprintf'.

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint