Graeme Geldenhuys schrieb:
On 15 July 2012 19:04, Michael Van Canneyt <mich...@freepascal.org> wrote:
Usually these things are private for a reason. But maybe there are better
reasons for doing it different, of course then I'd like to hear them first
:)
Yes, and I just wanted to point out that I some time ago I showed a
case where I needed to set ComponentState manually but couldn't... The
FPC team can't cover all possible use cases. Not everybody is creating
a Delphi clone application or framework, so there could very possibly
be a valid reason for doing something different to Delphi or Lazarus.
IMO it's a matter of component users vs. writers. A component writer
needs write access to some properties, which a user only should read.
The base class designers do not always see such needs, when they
implement everything in a single unit with lower protection boundaries.
Some members of TControl and TWinControl should be protected, not
private, and such a move won't change anything in user land.
DoDi
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
