* Shailesh Humbad:
Hello? I wouldn't have _any_ idea what in the world you were talking
about. And I do know both various assembly languages and C++.
Well that's incorrect however one looks at it.
Return address, sure. Almost any call pushes a return address. Except
on the MIX computer (do read your Donald Knuth).
Machine state? Only for an interrupt.
_Copies_ of function parameters? Nope, not at all. The function
parameters may be on the stack, but e.g. for Windows "fastcall"
convention they don't need to be there.
Space for local variables -- depends on whether ones thinks a
function prologoue is part of the _call_ or the _function_; I think
most people regard it as part of the function, because it's very
very easy to dip down to that level and put local variables
elsewhere, and the calls will still be the good old calls.
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?