Re: calling convention stdcalll and cdecl call
* Ben Voigt [C++ MVP]:
Anyways, as noted quite a few times already, why not pass on the
stack if you're afraid of that.
You said "in a register" and asked for an example of potential binary
incompatibility, which I provided.
You tried to provide an example and failed.
There is no such example and there can't logically be.
You can't break binary compatibility with non-existing code.
On what basis do you claim there is no existing code?
Please remember there is such a thing as context. The above quoting is out of
context. The claim you ask about has not been made.
At the very least the
example you posted in this thread earlier purports to be variadic stdcall
code,
It is stdcall code since it fullfills every criterion for stdcall.
And it is variadic.
and it exists in many mirrors of this newsgroup.
I'm not claiming and have not claimed there is no existing code; on the
contrary, this question has been asked a number of times before.
It's perhaps not clear from what you quoted above or had directly available to
quote from, but that includes the discussion with the person you quote from.
The context of that quote is breaking binary compatibility, which he mindlessly
maintained he had shown, not the existence of binary incompatibility, which one
needs to be pretty mindless to think does not exist or cannot exist.
I've said it's impossible to break binary compatibility be introducing support
for stdcall variadic functions.
And it is. ;-)
The logic is trivial: to break compatibility, you have to change something in an
existing usage.
And while there may in theory be existing code expressed in and used in some
other language implementation X, there is no existing usage for what you're
introducing support for, stdcall variadic functions in language implementation Y.
And just to address the point you raise, which is subtly different, it's
impossible to break binary compatibility (by introducing stdcall variadic
routine support) with the code I posted.
If there are any working calls to that code via some language implementation
support for stdcall variadic routines, those calls will continue to work just fine.
Cheers, & hth.,
- Alf
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?