"Freejack" <Freejack@nomail.com> a �crit dans le message news:
pan.2003.07.05.03.42.01.638542.1720@nomail.com...
> I've been picking through the GNAT docs (and Ada docs in general) in an
> attempt to figure out how/if and when/why the Ada compiler might choose to
> use an mmap system call in deference to a malloc/calloc or alloca call.
>
> Basically, I'm doing some low level routines and I need explicit control
> over what pages are swapped and when. ( mmap() mlock() munlock() and
> munmap() are the usual C functions for handling this.)
>
A common advice for this kind of issues is:
   Don't cheat.

If your need is to call mmap() (or whatever), just call it. Don't try to
second guess
some Ada statements that happen to do what you need today (but maybe not
tomorrow).

Ada statements are there to protect you from the underlying implementation.
If your need is to use a particular implementation (which I don't criticize,
there may be
plenty of good reasons for it), just do it openly.

--
---------------------------------------------------------
           J-P. Rosen (rosen@adalog.fr)
Visit Adalog's web site at http://www.adalog.fr