About extensible prinf(3), a slightly long X-mas card

[Poul-Henning Kamp]

In message <20051217102835.GC33190 at uk.tiscali.com>, Brian Candler writes:

>Perhaps the semantics of this extended printf() are so far divorced from the
>standard one that you might as well just call it something else? e.g.
>
>    ext_printf()

the reasons not to are

	ext_printf()
	ext_fprintf()
	ext_sprintf()
	ext_snprintf()
	ext_asprintf()
	ext_vprintf()
	ext_vfprintf()
	ext_vsfprintf()
	ext_vasfprintf()

There is little or no point in replicating all of this stuff.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.