Hello Lazarus-List,

All objects in the widgetset interface TWSxxxxx has the "class procedure" under the published section like:

TWSBitBtn = class(TWSButton)
published
  class procedure SetGlyph(const ABitBtn:...........
  class procedure SetLayout(const ABitBtn:..........
  class procedure SetMargin(const ABitBtn:..........
  class procedure SetSpacing(const ABitBtn:.........
end;

Is there any reason to be published instead public ? Maybe to garantee that the functions will never be removed by fpc/linker if not directly used in the code ?

there is a "virtual" classtree build based on RTTI. RTTI is only generated for published methods

Marc

Hello Lazarus-List,

you wrote

> Is there any reason to be published instead public ? Maybe to garantee > that the functions will never be removed by fpc/linker if not directly > used in the code ?

MW> there is a "virtual" classtree build based on RTTI. RTTI is only MW> generated for published methods

So this limits the possibility of the LCL to left out parts not being used in the program, as every class and method is references in some way by a published method.

And now the question :) should I in LCLfpgui move the public methods to published section (when ancestor is published of course) ? It is just to get a more hint clear compilation.

Yes, you correct. Thats one of the reasons of the big hello world. We will move this to interfaces someday after 1.0 or so.

And now the question :) should I in LCLfpgui move the public methods to published section (when ancestor is published of course) ? It is just to get a more hint clear compilation.

IMO yes.

Marc