[fpc-devel] passrc parser and published property accessors

[Michael Van Canneyt]

On Fri, 13 Aug 2010, Graeme Geldenhuys wrote:

> Hi,
>
> It seems that passrc parser doesn't populate the ReadAccessorName and
> WriteAccessorName correctly on published properties. eg: where a property
> was defined in a base class, and visibility simply bumped to published in a
> descendant class.
>
>
>  TButton = class(TBaseButton)
>  published
>    property ImageName;
>  end;
>
>
> With a result, the fpdoc documentation for TButton (in the linear writers
> at least) don't have Read or Write accessor information for
> TButton.ImageName property.
>
> Should the population of TPasProperty.[Read|Write]AccessorName be populated
> in the parser, or should fpdoc manage this itself, by trying to find the
> parent class with that property?

It should manage this itself. 
The parse tree should reflect the actual sources.

Michael.