Re: calling convention stdcalll and cdecl call
- From: "Alf P. Steinbach" <alfps@xxxxxxxx>
- Date: Fri, 18 Jul 2008 20:53:59 +0200
* Igor Tandetnik:
printf is a counterexample of what? It uses cdecl convention, where the caller is responsible for clearing up the stack. Consider also:
printf("%d", 1, 2);
How would your hypothetical stdcall printf know to remove 12 bytes worth of parameters, rather than 8?
I think you're stupid.
--
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?
.
- Follow-Ups:
- Re: calling convention stdcalll and cdecl call
- From: Igor Tandetnik
- Re: calling convention stdcalll and cdecl call
- References:
- Re: calling convention stdcalll and cdecl call
- From: Igor Tandetnik
- Re: calling convention stdcalll and cdecl call
- From: Alf P. Steinbach
- Re: calling convention stdcalll and cdecl call
- From: Igor Tandetnik
- Re: calling convention stdcalll and cdecl call
- From: Alf P. Steinbach
- Re: calling convention stdcalll and cdecl call
- From: Igor Tandetnik
- Re: calling convention stdcalll and cdecl call
- Prev by Date: Re: calling convention stdcalll and cdecl call
- Next by Date: Re: struct & enum & :: visibility operator
- Previous by thread: Re: calling convention stdcalll and cdecl call
- Next by thread: Re: calling convention stdcalll and cdecl call
- Index(es):
Relevant Pages
|