Re: Re: coding standards: Header Comment Blocks

Folks: I'm working on the next draft for this header comments RFC. A lot of folks were interested in seeing one of the phpDocumentor docblock @version tags contain the package release number as determined by the PEAR installer's replacement on @package_version@. While this sounds nice, I have some reservations. They didn't seem to be addressed, so I'd like to follow up. As mentioned before, it would force putting replace tags for each file into the package.xml file. I'm wondering why the installer doesn't just do the search/replace automatically without prompting from the package.xml. Similarly, why do the replacements while during the packaging, rather than the installing? (Let alone during packaging without prompting from the package.xml file.) (I have a feeling this has all been discussed before. :) ) Next, since the pacakging process can/does produce md5 sums for each file, doesn't the replacement upon installation cause the files' md5's to not match the recorded ones? Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409