🚀 go-pugleaf

In article <458@faatcrl.UUCP> jprad@faatcrl.UUCP (Jack Radigan) writes:
>jesup@cbmvax.commodore.com (Randell Jesup) writes:
>
>>	A note for all programmers out there: there is NO guarantee that
>>location 0 will be 0.  References to location 0 are bugs, and enforcer will
>>trap and report them.  Memmung stuffs a nasty value into location 0 to try
>>to break incorrect programs.
>
>Would've been nice if this was common knowledge *before* the 2091 hit the
>streets.  Alot of programs got bit by this problem, and more than a few
>were written by lawful coders too.
>
>  -jack-


If your program breaks when location 0 is non NULL this means
you have an unitialized pointer somewhere in your program, and
are using memory you did not allocate (ie location 0)

I would have hoped that this would have been common knowledge
amoung programmers long before the 2091 appeared.

			andy
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"If your ancestors were alive today, what they'd probably be saying is:
 'Where am I and why is it so dark ?' "
Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.