>"sfio" is not another "stdio variant" - it's completely different beast >(excluding the stdio emulation layer tacked on top of it, see Glenn's >posting about the reason for that). Please look at the manpages and >sources. >Another item for consideration is that libast acts as "portabilty layer" >which is mandatory to get ksh93/libshell running on various platforms >(AFAIK 30+). Sun didn't demand the removal of the portability layers in >Mozilla/Firefox, Gnome, Apache etc. prior their integration into Solaris >so I assume it's more than fair to not demand that from ksh93/libast, >too.
We may not "demand" the removal of the portability layers in Mozilla (Netscape Portable Runtime or some such), but we now that it a pile of junk and we know that such compatibility layers are best avoided. And while stdio has many shortcomings, it's what we have, know and love to hate. I don't think we want the AST stdio wrappers available for public consumption because this will always lead to confusion of the form "X bug in stdio" "can't reproduce", "oh, but we used AST stdio". We can't replace our libc stdio either; binary compatibility just doesn't allow it. Casper
