Path: utzoo!attcan!uunet!ginosko!ctrsol!emory!stiatl!tom
From: tom@stiatl.UUCP (Tom Wiencko)
Newsgroups: comp.lang.pascal
Subject: Re: TP50: Typed constants
Keywords: typed constants, debugging
Message-ID: <5984@stiatl.UUCP>
Date: 22 Jul 89 16:20:54 GMT
References: <1356@lafcol.UUCP>
Reply-To: tom@stiatl.UUCP (Tom Wiencko)
Organization: Sales Technologies Inc., "The Procedure IS the product"
Lines: 30

In article <1356@lafcol.UUCP> pilgrimk@lafcol.UUCP (Kenwyn A. Pilgrim) writes:
>Today I discovered something really bizarre.
>I had two typed constants which looked like
> ...
>My question is:
>  Is there a limit to the no. of typed constants?
>  (my data size was < 2K bytes according to the Get Info option)
>
>or what else do you think is wrong?
>
>-Kenwyn


Likely what has happened is that you are wiping out these memory locations
with some other modification of a typed constant.  A typed constant is 
not really much more than an initialized data area, and does not have any
size or count restrictions that I have ever read about or run into (and
I have some programs with lots and lots of typed constants).

First place I'd look is for pointers running away or some such like that.
The problem probably went away when you declared these items as variables 
because you changed their memory location.  A quick way to check this would
be to declare some large typed constants (large in size, not value) before
and after the affected constants and see if they are still getting clobbered.

This is a wonderful place to use the Turbo Debugger "breakpoint on changed
data" feature - probably one of the most powerful debugging features 
available in TD.

Tom