Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2010-08

passrc parser and published property accessors

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

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?

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Michael Van Canneyt
to Graeme Geldenhuys
Graeme Geldenhuys wrote 21 lines
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.

Reply by email