Re: Performance of access type : a tiny mistake in the WikiBook ?

[Gautier write-only <gautier_niouzes@hotmail.com>]

> I understand what you mean about testing, but I am mainly looking for
> average answers. Just things to know and to have in mind. Even if
> there is no required implementation, it is well known that a lot of
> compilers share some common implementation designs. I'm seeking for
> informations about it, just like the way I'm sometime reading about
> general tips or thoughts (I used to do the same with some prior
> languages like Pascal and Eiffel, it's a bit part of learning the
> thing).

So here is my rule: use only "in" (whenever possible), "in out" and
"out" and you will be happy.
These modes are meaningful for you and the compiler knows how to
handle it efficiently. Especially the compiler will consider passing
by copy, even through a register (and not on the stack), an "in"
parameter:

  procedure P_in(i: in Integer; s: in String) is
  begin
    Put_Line(Integer'Image(i));
    Put_Line(s);
  end;

The call P_in(5678,s) is compiled by GNAT GPL 2008 with (-gnatp -O2)
as:

        movl    %edi, %edx
        movl    %esi, %ecx
        movl    $5678, %eax
        call    _test_in_out__p_in.1893
_________________________________________________________
Gautier's Ada programming -- http://sf.net/users/gdemont/
NB: For a direct answer, e-mail address on the Web site!