Undelivered mail

[MAILER%ALASKA.BITNET at CUNYVM.CUNY.EDU]

Subject:  Re: nasty evil pointers

[Non-Deliverable:  User does not exist or has never logged on]

Reply-To: Info-C at BRL.ARPA

Received: From UWAVM(MAILER) by ALASKA with Jnet id 6552
          for SXJVK at ALASKA; Fri, 11 Mar 88 19:58 AST
Received: by UWAVM (Mailer X1.25) id 4393; Fri, 11 Mar 88 20:57:32 PST
Date:         Thu, 10 Mar 88 04:06:23 GMT
Reply-To:     Info-C at BRL.ARPA
Sender:       Info-C List <INFO-C at NDSUVM1>
From:         Patrick Bennett <null at bsu-cs.uucp>
Subject:      Re: nasty evil pointers
Comments: To: info-c at brl-smoke.arpa
To:           Vic Kapella <SXJVK at ALASKA>

In article <1159 at silver.bacs.indiana.edu>, backstro at silver.bacs.indiana.edu
(Dave White) writes:
> In article <13100003 at bucc2> brian at bucc2.UUCP writes:
> >
> >It would be nice if we could check every pointer as
> >it was used...
> >
> >
> >If pointer
> >pointed, say, into the operating system or the text space, the function
> >would print a message and exit(). Otherwise it would return.
> >

OS/2 provides this...  Different memory areas can have varying levels of
protection.  When this protection is broken, whether by attempting to modify,
read, whatever (depends on the protection) the program is promptly aborted but
with appropriate error info...

Although I personally don't have or use OS/2 I obtained this information from
the OS/2 Programmer's Guide by Ed Iacobucci (The leader of the IBM OS/2
Design Team)

Sounds great to me...

--
----
Patrick Bennett     UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!null