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

[VAXman- at SendSpamHere.ORG]

In article <o16tjq$e4b$1 at dont-email.me>, "Craig A. Berry" <craigberry at nospam.mac.com> writes:
>On 11/24/16 7:06 AM, VAXman- at SendSpamHere.ORG wrote:
>> In article <o15cvh$4oj$1 at dont-email.me>, "Craig A. Berry" <craigberry at nospam.mac.com> writes:
>
>>> I don't recall whether there are any native interfaces that use .ASCIZ
>>> but there are certainly MACRO programs that use it. And when coding in
>>> assembler, surely null-terminated strings are the least of your worries
>>> as far as accessing memory that doesn't belong to you. Which makes all
>>> the dumping on C kind of silly considering a third of VMS is written in
>>> a far more dangerous language. Dunno about BLISS. Maybe it's two thirds.
>>
>> What's more *dangerous*?
>
>The chances that a simple mistake will have you stomping on memory that
>doesn't belong to you or corrupting the stack.

Such as in C with all that crazy nested casting of pointers to pointers to
pointers to pointers?  ;)

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.