home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.pascal:6833 comp.object:4301
- Newsgroups: comp.lang.pascal,comp.object
- Path: sparky!uunet!cs.utexas.edu!torn!news.ccs.queensu.ca!slip204.telnet1.QueensU.CA!dmurdoch
- From: dmurdoch@mast.queensu.ca (Duncan Murdoch)
- Subject: Re: BP/TP OOP is missing something...
- Message-ID: <dmurdoch.183.722524736@mast.queensu.ca>
- Lines: 17
- Sender: news@knot.ccs.queensu.ca (Netnews control)
- Organization: Queen's University
- References: <1992Nov23.102238.18624@kth.se>
- Date: Mon, 23 Nov 1992 13:18:56 GMT
-
- In article <1992Nov23.102238.18624@kth.se> d85-jmh@dront.nada.kth.se (Jan-Olof Hendig) writes:
- >
- >Being able to detect NIL pointer dereferencing is a good reason to upgrade
- >to BP7. You 'just have to recompile' your programs with target set to
- >'Protected', and then run them. All NIL pointers that are dereferenced will
- >generate Runtime error 216, as will most illegal pointer operations, like
- >for instance using a noninitialized pointer. Protected mode has its benefits.
-
- You can detect bad pointers in TP 6, with the $R+ option. The only
- restriction is that they must be pointers to objects: pointers to other types
- aren't checked at all.
-
- Another couple of really nice additions to BP7 are typed "@", and overflow
- checking on arithmetic operations. Both of these have flushed bugs out of
- my programs.
-
- Duncan Murdoch
-