On Mon, 26 Jun 2006 07:46:26 -0400 James Carlson wrote:
> Dragging along another stdio that needs to be maintained doesn't quite
> fit that bill, regardless of why that implementation may be there or
> what other platform it happens to help.
neither ksh nor any other ast application/library uses stdio
so on solaris just don't advertize <ast/stdio.h>
and then deal with ksh93 libshell api developers with a blanket:
use <sfio.h> when developing libshell applications
for ksh (and ast etc.) the quality of a native stdio implementation
is not the issue; its the inadequacy of the stdio api itself:
buffer management
efficient (and painless) use of memory mapping
the relationship between streams and file descriptors
string streams
string stacks
stacked disciplines
exception handling
printf disciplines (e.g., for implementing printf(1))
some non-standard stdio implementation are catching up
(in mutually incompatible ways) -- we had this resolved in 1990
solaris does not have to use sfio
but it will have to accept that ksh will
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
