Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcvax!hp4nl!dutrun!winfave
From: winfave@dutrun.UUCP (Alexander Verbraeck)
Newsgroups: comp.lang.pascal
Subject: Re: TP50: Typed constants
Keywords: typed constants, debugging
Message-ID: <809@dutrun.UUCP>
Date: 23 Jul 89 16:12:50 GMT
References: <1356@lafcol.UUCP> <5984@stiatl.UUCP>
Reply-To: winfave@dutrun.UUCP (A.Verbraeck)
Organization: Delft University of Technology, The Netherlands
Lines: 21

In article <5984@stiatl.UUCP> tom@stiatl.UUCP (Tom Wiencko) writes:
>> ...
>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).
>
>Tom

Except of course for the general restriction of 64 kb per structure!
I would define a typed constant as a variable with an initial value. At
least, that is what I am using it for normally.

---------------------------------------------------------------------
Alexander Verbraeck                            e-mail:
Delft University of Technology                 winfave@hdetud1.bitnet
Department of Information Systems              winfave@dutrun.uucp
PO Box 356, 2600 AJ  The Netherlands
---------------------------------------------------------------------