On 2006-04-20, Tony Wyatt wrote: <SNIP>
Well, the newlib library is shared, which means that only a single memory-resident instance is required. All applications using it can call the resident instance without having to load the library themselves. Hence each application is MUCH smaller than it would be using clib.
clib2 is _maximum_ 1MB which in contrast to the size of the OO.o suite is not very much. The OO.o _install package_ is already >100MB in size (size taken from the Solaris/SPARC install package) so using clib2 or newlib would probably make less than 1% difference in size.
The benefits of clib2 are easier porting and this in turn means that we already have a working port if we wish to switch to newlib later. (And half the work will already have been done making it easier)
The only caveat that I can think of is that one of the two (clib/newlib) is thread-safe, the other is not. That fact alone more or less forces our hand towards using one or the other. Damned if I can remember which is which.
Early versions of clib2 were not thread-safe. There is now both a thread-safe and a non-thread-safe version of clib2. Newlib has always been thread-safe (it has to be) .
-Peter aka. Archprogrammer
Reality is for people who cannot face ScienceFiction. Only lefthanded people are in their right minds.