Hi,
as some of you have noticed I currently working on mod_perl's XS generation
system. One thing I have done is to replace C::Scan with an parser based on
Parse::RecDescend. One benefit of this is, that it is very easy to extent
what is parsed. So additionaly to the function and structures I currently
also extract the comments that belongs to these functions and structures and
lot of these comments contains the Aapache API documention in a special
format to create the documention files from them. So why don't we use these
comments to auto generate the pod files from them. The result has of course
to be reviewed manualy and corrections have to made, to adopt it to the Perl
interface, but this could be done in a similar way like it is done for the
XS code, by having some sort of map files, which contains additional docs or
changes on a function to function basis. That would saves a lot of
documention handwriting.
What do you think ?
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
as some of you have noticed I currently working on mod_perl's XS generation
system. One thing I have done is to replace C::Scan with an parser based on
Parse::RecDescend. One benefit of this is, that it is very easy to extent
what is parsed. So additionaly to the function and structures I currently
also extract the comments that belongs to these functions and structures and
lot of these comments contains the Aapache API documention in a special
format to create the documention files from them. So why don't we use these
comments to auto generate the pod files from them. The result has of course
to be reviewed manualy and corrections have to made, to adopt it to the Perl
interface, but this could be done in a similar way like it is done for the
XS code, by having some sort of map files, which contains additional docs or
changes on a function to function basis. That would saves a lot of
documention handwriting.
What do you think ?
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org