[lazarus] designer.inc file error

Marc Weustink weus at quicknet.nl
Tue Mar 21 19:10:56 EST 2000

At 18:46 21-03-2000 -0500, Michael A. Hess wrote:
>Marc Weustink wrote:
> >
> > I guess accessing protected or private members of classes defined in
> > the same unit is stil valid, but not if they are originally defined in
> > another unit ???
>As defined in our wonderful FPC documentation.   ;-)
>Private  - All fields and methods that are in a private block, can only
>            be accessed in the module (i.e. unit) that contains the class
>            definition. They can be accessed from inside the classes'
>            methods or from outside them (e.g. from other classes'
>            methods)
>Protected  - Is the same as Private, except that the members of a
>              Protected section are also accessible to descendent types,
>              even if they are implemented in other modules.

Then I don't understand where the compiler is complaining about, since the 
protected member we are accessing is a member of a class which is defined 
in the same module.
If protected is the same as private (only more visible) then also counts 
that protected members are visible outside the class, which seems not the 
case now.

I have to admit, this is a somewhat strange behaviour whithin the object 
model, but IMHO it is something what should be controlled by some kind of 
If not we might end up with all units together in one big unit.


More information about the Lazarus mailing list