Paul Davidson wrote:
If there compelling reason why type definitions cannot be included in
class/object definitions?
Make it mode FPC to keep folks happy :)
Quite often a type is defined in INTERFACE part, but only used within
class/object defined in same unit.
1) This means that type is public. This is not always good thing in
OOese.
2) Unit must be specified in child's child's USE list.
P Davidson
Corax Networks Inc.
http://CoraxNetworks.com
IMPORTANT NOTICE: This message is intended only for the use of the
individual or entity to which it is addressed. The message may contain
information that is privileged, confidential and exempt from
disclosure under applicable law. If the reader of this message is not
the intended recipient, or the employee or agent responsible for
delivering the message to the intended recipient, you are notified
that any dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this communication in
error, please notify Corax Networks immediately by email at
[EMAIL PROTECTED] Thank you.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
I second this request. Throw in const fields too..
Ales
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
