[Info-vax] Calling standards, was: Re: Byte range locking - was Re: Oracle

[Bob Koehler]

In article <o16tjq$e4b$1 at dont-email.me>, "Craig A. Berry" <craigberry at nospam.mac.com> writes:
> 
> The chances that a simple mistake will have you stomping on memory that
> doesn't belong to you or corrupting the stack.

   User mode code doesn't get to stomp on any memory that doesn't belong
   to it under any OS using an MMU that I've looked at in a long, long
   time.

   Corrupting the stack is a lot less likely when you explicitly know
   you're using the stack.  How many C programmers do I have to deal
   with that have no concept of the implications that local variables
   default to the stack and calling arguments generally do, too?