[fpc-devel] class constants
JoshyFun
joshyfun at gmail.com
Mon Oct 19 20:39:53 CEST 2009
Hello Vinzent,
Monday, October 19, 2009, 1:59:06 PM, you wrote:
VH> Of course, as you state, the visibility provided by the unit
VH> might be enough. But it also means, that a derived class may need
VH> to include that unit whereas in case of a class constant, it
VH> wouldn't need to. Not that this is a particularly strong argument.
VH> ;)
When writting generic classes (not generics) I usually had to write in
fact 2 files:
MyUsefulclasses.pas and MyUsefulclasses_types.pas
Of course the information in the second file are "private" constants
and types for the first file classes. A non exportable zone of the
code at the beginning of the unit will solve most of this "problems",
as private types and private consts are for a given class. In the
spirit of pascal (from my point of view) would be more logical to have
a private zone in the interface zone, specialy for types.
Just adding my 2 cents fo noise to the thread :)
--
Best regards,
JoshyFun
More information about the fpc-devel
mailing list