Re: "new" word

["fabio de francesco" <fmdf@tiscali.it>]

Adrian Knoth wrote:
> Vinzent 'Gadget' Hoefler <nntp-2005-03@t-domaingrabbing.de> wrote:
>
> [new via malloc of libc]
> > so why should one write an Ada specific memory allocator that
>
> To get rid of libc, C and all this? ;) A native kernel interface
> would be nice to eliminate possible implementation errors in libc.
>
> On the other hand as far as I can see there is no binary
representation
> of the linux-kernel, in other words, you'll need to dynamically
> adapt the Ada memory layout to the corresponding kernel (+compiler).

No, it isn't required. You don't need a Kernel-ABI in order to access
system calls in kernel space, as I wrote in another post in this
thread. There is a standardised way to access syscalls through
interrupt H80.

Imagine you write a new syscall in Linux kernel and you want to use it
before it is binded into the LibC, you can do it with some simple
Assembly inline C/C++/Ada and whatever else programming language.

Same way you can access sys_sbrk() that is the standard syscall that
provide memory in user space.

fabio de francesco


>
> Another way would be to specify the Kernel-ABI, but I don't expect
> this to happen earlier than Hurd ;)
>
> AdaOS would probably come along with a well-defined ABI and no
> libc, but libada.
>
>
> --
> mail: adi@thur.de  	http://adi.thur.de	PGP: v2-key via keyserver
> 
> Mit leerem Kopf nickt es sich leichter.