On 18-11-2011 12:23, Graeme Geldenhuys wrote: > On 2011-11-18 13:15, Reinier Olislagers wrote: >> >> So apparently no help for the poor developer who wants to inherit a >> class and wants to figure out how to use the protected methods & >> properties ;) > > The is also no help (near zero) for poor Michael, having to write all > that documentation. Just documenting the Public and Published parts, was > already a huge undertaking - and there are still more units that are > completely undocumented (as you might know). So documenting the most > used parts first, seem like a good path to take. ;-) Oh, I completely agree that's the most sensible path.
Thought I could add some titbits while doing a search for Visibility: public, Visibility: default and Visibility: published. At least I tried... Let me put it another way: when I have time, the inclination and knowledge and if it is actually fairly easy to do, I'll propose a patch for makeskel that changes function result Visibility: default into function result Visibility: private, protected, public or published, depending on scope of the parent function and argument Visibility: default into argument Visibility: private, protected, public or published, depending on scope of the parent procedure/function ... unless the FPC gurus object to it Now back to the grindstone... _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal