🚀 go-pugleaf

In article <DFs6G0.FF@stdc.demon.co.uk>,
clive@stdc.demon.co.uk (Clive D.W. Feather) wrote:
>>> The symbol printf will always be reserved, but there is no guarantee that
>>> the function will be available to the programmer in a freestanding
>>> implementation.
>> Is the same true of sprintf?  I can see why printf might cause
>> difficulty in a freestanding environment, but not sprintf.
>
>Yes. It's not a question of difficulty, but principle.

In practice, implementations designed for embedded use (not hosted)
incorporate most of the non-locale-extended library anyway, including
sprintf.  In fact, most provide stdin and stdout I/O routines, simply
letting the user supply getchar() and putchar(), or something
equivalent.  An implementation that did not provide at least the old
non-wchar functions in <string.h> would be considered inferior, even
though it could claim ISO C freestanding compliance.

Thad