Re: Where are returned values stored?

[Martin Krischik <krischik@users.sourceforge.net>]

Larry Kilgallen wrote:

> In article <60328483.MtZnWf8h2m@linux1.krischik.com>, Martin Krischik
> <krischik@users.sourceforge.net> writes:
>> Warren W. Gay VE3WWG wrote:
>> 
>>>  > Interesting to consider this with a recursive procedure, but yes, it
>>>  > should work.
>>>  >
>>>  > JAF
>>> 
>>> Calling Conventions:
>>> 
>>> If this indeed happens (on a given platform), I would think
>>> that the calling convention used is +critical+. For example,
>>> if you forced an Ada routine to use the C calling convention,
>>> I would bet that on most platforms, that all return values
>>> must be _copied_ or placed on the heap (temporarily). At least
>>> this would be true for strings/arrays etc. where the size
>>> was not known in advance.
> 
> Just jumping in, this seems to be an OS-independent discussion.

The OP is involved in C - Ada mixed language programming.

>> The "C" calling convention places the return value inside a hidden static
>> variable. A pointer to this variable is then returned.
> 
> I am not sure what you mean by "the" C calling convention.

Whatever K&R though is practical for there programming language. For use
from Ada see also RM B.3 (1/1).

> Certainly on VMS C obeys the OS calling convention for all inter-module
> calls, just as other languages do.

As does Windows and OS/2. It seems that almost everywhere the C compilers
don't use calling convention "C" anymore for anything but printf and scanf.

With Regards

Martin

-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com