Hi,
I comment my code using the pasDoc syntax and generate HTML files. I
am thinking of moving over to fpDoc LazDoc, but have a few
questions.
What happens to the documentation when I refactor my code? Example:
Move classes to another unit, or drop methods in a class which where
documented
On Wed, 5 Jul 2006, Graeme Geldenhuys wrote:
Hi,
I comment my code using the pasDoc syntax and generate HTML files. I
am thinking of moving over to fpDoc LazDoc, but have a few
questions.
What happens to the documentation when I refactor my code? Example:
Move classes to another unit, or
Thanks!
BTW: I just ran fpdoc against my code and the html didn't look like
the FPC or Lazarus documentation. A close look at the HTML, I noticed
that it is referring to a non-existent fpdoc.css stylesheet.
Is fpdoc supposed to create that on the fly? If not, wouldn't it be a
good idea,
Graeme Geldenhuys schreef:
Thanks!
BTW: I just ran fpdoc against my code and the html didn't look like
the FPC or Lazarus documentation. A close look at the HTML, I noticed
that it is referring to a non-existent fpdoc.css stylesheet.
Is fpdoc supposed to create that on the fly? If not,
On Wed, 5 Jul 2006, Graeme Geldenhuys wrote:
Thanks!
BTW: I just ran fpdoc against my code and the html didn't look like
the FPC or Lazarus documentation. A close look at the HTML, I noticed
that it is referring to a non-existent fpdoc.css stylesheet.
Is fpdoc supposed to create that on
2006/7/5, Graeme Geldenhuys [EMAIL PROTECTED]:
On 7/5/06, Vincent Snijders [EMAIL PROTECTED] wrote:
I am not sure it is a good idea. It would overwrite custom stylesheets.
If one exits, don't overwrite it. If not, create one (if will look
better than not having a stylesheet at all). One
