Felix Schulte wrote: > On 6/25/06, Casper.Dik at sun.com <Casper.Dik at sun.com> wrote: > > This seems wrong; personally I think we should rip out any replacement > > for system libraries; such duplication leads to more code which needs > > to be maintained. This includes replacements for <stdio.h>. > There would be no need to replace it if the stdio implementation in > Solaris would be sane, however since it sucks a faster, non-sucking > replacement would be cool.
And what exactly "sucks" in Solaris stdio ? Please list examples... > > (The problem is even bigger if these are indeed shipped as part of > > the ksh libraries; having multiple implementations visible to processes > > is bad; note that re-exporting symbols like fopen() would be blatantly > > illegal in C and therefor also in Solaris; our libraries will malfunction > > when they find a different stdio library) > No, they won't malfunction. All AST stdio symbols have an '_ast_' > prefix in their ELF name, for example fopen() is listed as _ast_fopen > by elfdump Yes (except for two functions (|wordexp()| and |regexp()|) but that's a small and easy to fix bug) ... which why I am start wondering why people are complaining here. Just because the headers have the "std*"-prefix in their names ? They live - intentionally - in another directory and are clearly labeled. ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
