Nahun wrote
>
> You can do it at the Method level in delphi by declaring
> {$WRITEABLECONST ON} which esentially makes the const a
> static for the scope of the method
And Matt wrote
>
> In the unit the Class is defined, have a variable located
> in the Implementation section that the methods read/write
> to.
Which made me think that I can, of course, declare a property with whatever scope is
required in the base class who's getter/setter accesses a variable or typed constant
declared in the implementation section. Properties are de facto variables so problem
solved!
A bit more thought about it, and I realized that the VB (and C#, C++ I imagine) method
of achieving this is necessary since they don't have the equivalent of an
implementation system. All this stems from the fundamental difference between single-
and multi-parse compilers, I suppose.
Paul wrote
> Delphi has class functions and class methods, but not
> class members.
The VB meaning of "Class member" is not the same as we would think of it in Delphi,
since it is only applicable to instances.
Well, that was a nice diversion for a Friday afternoon - better get some real work
done.
Bob Osborn
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
