Re: Function order of execution
From: Kurt Barthelmess (kbarthelmess_at_compuserve.com)
Date: 11/21/03
- Next message: Kurt Barthelmess: "Re: Function order of execution"
- Previous message: Mike Williams (TeamB): "Re: Function order of execution"
- In reply to: Sven Pran: "Re: Function order of execution"
- Next in thread: Kurt Barthelmess: "Re: Function order of execution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 21 Nov 2003 21:40:38 GMT
"Sven Pran" <no.direct@mail.please> wrote:
>I seriously suspect that this implication was never intended by the writer
>of the calling conventions when he used the word "evaluate".
I agree. Nor did (s)he understand the implications. This may be a WAD,
a boo-boo on the part of the author, or a Delphi bug.
>It just makes no sense to prepare the EAX register with reference to
>(or value of) the first parameter while still probably being needed to
>prepare other parameters in the list.
Even worse, one can not simply "push" the first parameter onto the
stack to hold it and then pop it back into EAX. By that time you could
have umpty-ump things on the stack (parameters 4, 5, 6...) Still, it
wouldn't be that inefficient to push it onto the stack, load it from
the stack make the call and then pop the 1-3 entries. That's no worse
than the stuff that happens when you do something like:
P(String1 + String2);
Kurt
- Next message: Kurt Barthelmess: "Re: Function order of execution"
- Previous message: Mike Williams (TeamB): "Re: Function order of execution"
- In reply to: Sven Pran: "Re: Function order of execution"
- Next in thread: Kurt Barthelmess: "Re: Function order of execution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|