Re: [dev] on a potential libc replacement

On Tue, May 26, 2009 at 05:13:23PM +0200, Szabolcs Nagy wrote:
>"A cross platform implementation, that should replace existing
>implementations of the system core libraries"
>posix syscalls cannot be implemented in a cross platform way, they
>depend on system internals

It's possible to write portable code that utilizes platform (or
architecture) specific code. You need to segregate the portable
portions from the unportable portions, so that porting only
requires writing some system call stubs for each new host OS,
and some other assembly language stubs for each new
architecture. See, well, most of Plan 9.

>i wonder what they mean by portable, because even the c std lib can
>not be implemented in pure c: malloc or setjump depend on system
>internals or syscalls, or memcpy etc should be optimized for the cpu
>architecture..

Malloc can be implemented in pure C, assuming that the library
already implements mmap or sbrk.

-- 
Kris Maglione
[As for the <BLINK> tag,] it was a joke, okay?  If we thought it would
actually be used, we wouldn't have written it!
	--Mark Andreessen