Peter Memishian wrote: > > At least libnsl and libsocket are still seperate libraries since they > > are far too big (and IMO they should remain seperate since not every > > application needs networking) > > We (Solaris Networking) are seriously considering folding libnsl and > libsocket into libc.
Ouch... Ok... ... some notes/questions for that work: 1. It would be nice to move ONLY the current POSIX-based and other standards-based functionality (Unix98 etc.) libnsl+libsocket functions to libc and keep all the compatibilty-wrapper stuff in libnsl/libsocket to avoid that libc gets bloated with 20years of Unix backwards-compatibility workarounds 2. Maybe [1] could be extended to the non-reentrant/threadsafe versions of some functions, e.g. |gethostbyname_r()| moves to libc, |gethostbyname()| remains in libnsl (OkOk, this is just dreaming/wishfull thinking... but such a "split" would avoid adding more global read/write data to libc and may even influence application programmers to use the |*_r()| interfaces by default) 3. What are the reasons for such a "fold" ? 4. What about (as alternative propsal OR executed as part of the "folding") to compile the libnsl/libsocket code with "-xstrconst" + some further linker magic to reduce size of the data which need to be duplicated for each process ? ---- Bye, Roland P.S.: Reply-To: set to [email protected] (please disucss the details there) ... -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
