Gerhard Fiedler wrote:
> This seems to assume that a constant remains constant, which in the
> above isn't the case. He didn't try to access globConst under that name,
> but if the "absolute" directive does what I think it does, its value
> will have changed after the last cited line above.

I don't know what "absolute" is supposed to do, but V3 looks like it's being
defined as a variable and only initialized with the contant value, which is
very different from being a constant such as globConst.

> And the 'real' constants don't seem to have a type, similar to
> the preprocessor #defines in C. Not good either; in a strongly typed
> language, constants should also have a type. Well... nothing's perfect
> :)

I don't know the definition of his language, but in my Pascal CONSTs
certainly have a type.  They have whatever type the constant expression
resolves to.  For example:

const
  a = 'z';
  b = 27;
  c = 3.14;

A will have a type of character, B of integer, and C of floating point.  The
exact format or size of integer and floating point doesn't matter since they
are symbolic constants only and have no inherent realization.  The compiler
can of course create literals for them when needed, but there is no
guarantee that the same memory location will be used for the literal each
time.  The constant value could even be encoded in the immediate value of a
instruction.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist