Next: srfi intermediate-format rationale, Previous: srfi intermediate-format abstract, Up: srfi intermediate-format [Index]
Some may disagree with specific escape options or return values. For
those who desire complex options as implemented by SLIB or Common Lisp’s
format
, an upwards compatible “Advanced Format” SRFI should
be proposed.
In particular, the reference implementation given here does not accept
numeric arguments (aside from ~F
). Hence it does not support
SRFI-29.
It is highly desireable that baseline library code be small, attempt to
eliminiate heap allocation and bound stack usage. This is especially
important in embedded systems. This can be accomplished by writing
directly to a port, rather than a string, by not supporting ~W
or
~F
, and by replacing:
(display (number->string n r) p)
with a carefully written:
(display:number->string n r p)
which does not build intermediate strings.
As this is intermediate format, it was felt that ~F
and ~W
are too highly useful to elide. The ~H
option is helpful to
users, allows for programattic query, and makes clear which format
directives are supported.