Re: Re: coding standards: Header Comment Blocks
| From: | Daniel Convissor | Date: | Tue, 08 Jun 2004 15:42:24 +0000 |
| Subject: | Re: Re: coding standards: Header Comment Blocks | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-30179@lists.php.net to get a copy of this message | ||
Hi Folks:
On Tue, Jun 08, 2004 at 10:32:53AM +0200, Tobias Schlitt wrote:
>
> Hi Tomas V.V.Cox! You wrote:
>
> > You can use the PEAR package replace capabilities. Ex:
>
> > * @version @package_version@ (CVS rev: $Id:$)
>
> > and in package.xml
>
> > <file name="Class.php">
> > <replace from="@package_version@" to="version"
> > type="package-info"/>
> > </file>
So, we'd have to put the replacement tags in each file and put in replace
elements for each file in the package.xml file. A headache and another
vector for potential errors.
The JavaDoc standard is to use CVS $Id$ keyword. It's simple to
implement.
> This should be worth an RFC. Does anyone volunteer to provide it?
An RFC seems to be overkill to me. We can reach agreement here and just
put it in the coding standards.
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