Hi Mark,
On 19/04/2006, you wrote:
Peter,
One important thing to be sure of, before we start with the different libraries... what c-library should we use?
The size difference would be miniscule and as an initial effort towards porting I have been looking at extending clib2 with useful functions. (and have contributed a few functions, e.g. the termios emulation)
I vote that we concentrate on using clib2 to begin with.
Ahh good a proponent for the other side ;-) feel fre to answer my previous question re any downside to starting with clib2 and moving to newlib later.
Also everybody feel free to butt in with their opinion, I'll way up the pros/cons and let the programmers decide when we get that far ;-) (or I may jst make a descision ;-) )
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.
The newlib library is being adopted as the standard library for OS4 applications. To this end, one can assume that in the future, newlib will already be memory-resident by the time any applications feel the urge to call it, reducing app size and hence load time.
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.
cheers