(Well, in fact, I don't know why you posted this information since
there are no comments or questions with it... so if my answer is out
of your mail intention, sorry. I can't see to who you were replying.
Best regards.)
2006/6/9, Alexandre Leclerc <[EMAIL PROTECTED]>:
Hi Gabor,
We are talking about classes interfaces/definition, not about class
implementation and actual usage. This documentation is good in the
implementation section and while using the class.
When you "subclass" you can reimplement any "level of visibility" of
the ancestor class and also change this "level of visibility", but
only downward (more private, never mor public).
Hope this helps.
Best regards.
2006/6/9, Gabor Boros <[EMAIL PROTECTED]>:
>
> From FPC's Reference Guide:
>
> 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.
>
> Public
> sections are always accessible.
>
> Published
> Is the same as a Public section, but the compiler generates also type
> information that
> is needed for automatic streaming of these classes. Fields defined in a
> published section
> must be of class type. Array properties cannot be in a published section.
> *******************
>
> Gabor
>
> _________________________________________________________________
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject
> archives at http://www.lazarus.freepascal.org/mailarchives
>
--
Alexandre Leclerc
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
