Path: utzoo!mnetor!uunet!husc6!bbn!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!brl-adm!adm!MAILER%ALASKA.BITNET@CUNYVM.CUNY.EDU From: MAILER%ALASKA.BITNET@CUNYVM.CUNY.EDU Newsgroups: comp.lang.c Subject: Undelivered mail Message-ID: <12269@brl-adm.ARPA> Date: 12 Mar 88 05:23:04 GMT Sender: news@brl-adm.ARPA Lines: 44 Subject: Re: nasty evil pointers [Non-Deliverable: User does not exist or has never logged on] Reply-To: Info-C@BRL.ARPA Received: From UWAVM(MAILER) by ALASKA with Jnet id 6552 for SXJVK@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@BRL.ARPA Sender: Info-C List From: Patrick Bennett Subject: Re: nasty evil pointers Comments: To: info-c@brl-smoke.arpa To: Vic Kapella 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: !{iuvax,pur-ee,uunet}!bsu-cs!null