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

[VAXman- at SendSpamHere.ORG]

In article <v4LIbJSXWttc at eisner.encompasserve.org>, koehler at eisner.nospam.decuserve.org (Bob Koehler) writes:
>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.

I write inner mode code and I'd wager that I am far more aware of what memory
I am using than the casual user mode C coder.



>   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?

... and, in assembly or Macro, I'm far more cognizant of the stack too.
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.