Xref: utzoo comp.lang.c:7483 comp.sys.ibm.pc:12222
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!batcomputer!sun!nelson
From: nelson@sun.soe.clarkson.edu (Russ Nelson)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: MSC Danger (was Re: Turbo C vs Quick C)
Keywords: good better best
Message-ID: <450@sun.soe.clarkson.edu>
Date: 21 Feb 88 19:56:18 GMT
References: <389@lscvax.UUCP> <567@naucse.UUCP> <2946@dasys1.UUCP> <443@siemens.UUCP> <112@westmark.UUCP>
Reply-To: nelson@sun.soe.clarkson.edu.UUCP (Russ Nelson)
Organization: Clarkson University, Potsdam, NY
Lines: 12

In article <112@westmark.UUCP> dave@westmark.UUCP (Dave Levenson) writes:
>MS-C release 3.0 and 4.0 also check for NULL pointer references at
>runtime.  They do this by [checking..] the first sixteen bytes of the data
>segment. If they don't compare, the runtime package displays the
>message "NULL POINTER REFERENCE" as your program exits.

Turbo C does this also.  Perhaps what the original poster meant was that
MS-C 5.0 checks *every* pointer use for the null pointer.
-- 
-russ
AT&T: (315)268-6591  BITNET: NELSON@CLUTX  Internet: nelson@clutx.clarkson.edu
GEnie: BH01  Compu$erve: 70441,205