Michael Van Canneyt wrote:
If so, what side-effects would this cause when applied across the complete
class-hierarchy?
Blow up the size of you executable.
And a virtual method call is slower than a non-virtual call. (as it needs to do
a few lookups: class, VMT)
To ensure self is not nil, you can insert a check in a method itself. However,
you cannot defend yourself against an invalid (but non-nil) object pointer.
(I.e. a pointer to an object that is freed already.)
Bram
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
