On 09/08/2014 01:03 PM, Ivanko B wrote:
Starting to work on the descriptions files
=
What will they contain ?
To start with the documentation generated from fpdoc will look like the
free pascal documentation:
http://www.freepascal.org/docs-html/rtl/objects/tobject.html
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's a deal of half of a minute but saves
many hours nerves in
On 09/08/2014 01:55 PM, Ivanko B wrote:
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's a deal of
And just who would place the comments in the code for the PasDoc program?
Would that be Martin?
==
Anyone allowed to edit the sources (via rollable back GIT commits for
sure). Or dedicated patches to send to Martin for applying by him.
Currently those may be others than Martin but
Also The PasDoc way won't make sources dirty since one will take only
beginning (declaration) part of files.
But PasDoc should be tested for correct propagating inherted methods
props and hiding private ones while generating DOC data - so that
each (own inherited) public/protected/published
On Monday 08 September 2014 19:55:11 Ivanko B wrote:
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's
6 matches
Mail list logo
