Furthermore, I think my example could still beneficially be used to insert things like function sysopsis, which aren't dependent on writing style, just on arguments etc.
That's for the template that will be used for creating the auto-docs, no?
No, for the final docs (must be run through a template engine though). API changes will then reflect automatically in the function synopsis, although manual addition of description might be needed. I'm not sure if this method is better/worse than your diff method though. My point was just that whatever we do, the only thing remaining from the auto-generation will probably be the function synopsis, as descriptions will be modified to Perl jargon. Like this we would only go through a make.pl (or something like that) stage, not the "update, diff, patch" sequence.
The function synopsis will be needed to be adjusted for certain functions. We change certain C API the Perl way, so I think this idea simply won't work and cause more trouble than help.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
