Path: utzoo!mnetor!uunet!husc6!think!ames!pacbell!att-ih!ihnp4!inuxc!iuvax!bsu-cs!null
From: null@bsu-cs.UUCP (Patrick Bennett)
Newsgroups: comp.lang.c
Subject: Re: nasty evil pointers
Message-ID: <2315@bsu-cs.UUCP>
Date: 10 Mar 88 04:06:23 GMT
References: <13100003@bucc2> <1159@silver.bacs.indiana.edu>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 26

In article <1159@silver.bacs.indiana.edu>, backstro@silver.bacs.indiana.edu (Dave White) writes:
> In article <13100003@bucc2> brian@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