[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [f-cpu] calling conventions



On Fri, 7 Jun 2002 02:57:16 +0200, Christophe wrote:
>
>> E.g. open() is often declared as
>>
>> int open(const char *name, int mode, ...);
>>
>> (because it can take two or three arguments) but in fact it may be
>> (and eventually is) implemented as
>>
>> int open(const char *name, int mode, int perms) {
>> ...
>> }
>>
>> These two declarations must be compatible, or else a lot of
>>`legacy'
>> C code will break.
>
>Okay, now I do know why GCC always refuse to mix register and stack
>parameters,
>because of the sacrosanctity of this ugly legacy.
>
>Well, I must admit that I don't like this calling convention but
>regarding with
>your last argument, more intelligent rules are things best
>forgotten. Sorry for
>annoying you so much.
>

I'm sorry but Delphi and Kylix mix register and stack parameters in their
calling convention and all work OK without any problems. It's a very
speed call system and simple to use.

--
Thomas Lavergne                       "Le vrai rÍveur est celui qui rÍve
                                       de l'impossible."  (Elsa Triolet)
thomas.lavergne@laposte.net                                      
d-12@laposte.net    ICQ:#137121910     http://assoc.wanadoo.fr/thallium/


*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/