Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!nrl-cmf!ukma!psuvm.bitnet!cunyvm!ndsuvm1!ndsuvax!ncsmith
From: ncsmith@ndsuvax.UUCP (Timothy Smith)
Newsgroups: comp.lang.pascal
Subject: Re: pointers about TP pointers
Message-ID: <2004@ndsuvax.UUCP>
Date: 5 Jan 89 00:36:07 GMT
References: <2775@k.cc.purdue.edu> <7071@batcomputer.tn.cornell.edu> <3271@arcturus>
Reply-To: ncsmith@ndsuvax.UUCP (Timothy Smith)
Organization: North Dakota State University, Fargo
Lines: 18


reply to S. Kulikowski on Turbo pascal pointers:

    I have found the pointers in TP3 - TP5 to works reliably and just
how I tell them to.  Now barring any non-obvious errors in the pointer
code I have found the biggest area where problems can occur in pointer
intensive code is around declared arrays.  No version of TP defaults to
checking the range of a subscript for an array so if you declare a
pointer variable after an array and access a cell that exceeds
the upper bound on the array your pointer could be trashed.  Of course
anything else after it could be trashed including code if the subscript
is right.  So rather than bash the complier, check out your array code.

ps: this is a second sending as the first got mauled somewhere around
    rutgers.
--
Tim Smith     North Dakota State University,  Fargo, ND  58105
UUCP:         ...!uunet!ndsuvax!ncsmith | 90% of the people on this planet
BITNET:       ncsmith@ndsuvax.bitnet    | are crazy and the rest of us are
INTERNET:     ncsmith@plains.NoDak.edu  | in grave danger of contamination