🚀 go-pugleaf

In article <4kr78t$kao@solutions.solon.com>,
Casper H.S. Dik - Network Security Engineer <Casper.Dik@Holland.Sun.COM> wrote:
>Yes, it seems that the format call back function (bangcvt) should take
>a number of flags (leading 0/- found, precision, maximum width) and
>a generic way to make the user defined format specifier output characters,
>as it can be called from functions like "snprintf", which limit the output.
>Passing a buffer to but the output in doesn't strike me as sufficient;
>if "bangcvt" can have unlimited output, it must be possible for the
>mechanism to cater for that.

But, of course, the current language only guarantees up to 509 characters.

It does get the flags; a fmtspec is a struct containing those and other
info.

>And, of course, you want a input conversion as well :-)

Still working on that.

>So instead of:

>You'd get something more like:

>    bangcvt (va_list *ap, int flags, int width, int precision,
>	char fmt, int (*putit)(char c, void *output), void *output)

>(Where you call "putit" for each character of output with *output
>as magic for the call back)

The problem is that function calls tend to be expensive.  The flags,
width, and precision are already in the fmtspec *.

-s
-- 
Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
C/Unix wizard -- C/Unix questions? Send mail for help.  No, really!
FUCK the communications decency act.  Goddamned government.  [literally.]
The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html