Re: Re: coding standards: Header Comment Blocks
| From: | Greg Beaver | Date: | Tue, 08 Jun 2004 18:33:00 +0000 |
| Subject: | Re: Re: coding standards: Header Comment Blocks | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-30197@lists.php.net to get a copy of this message | ||
Tomas V.V.Cox wrote:
Stephan Schmidt wrote:moooowahahhahaha....Hi,In this cases, replacements should need some regulations unless Greg learned black magic.+10 on this solution. This should become general standard for all packages and files.Is the file version always identical with the package version? I will not adopt this for my packages, unless PEAR_PackageFileManager automatically does this, as I always generate the filelist and I would have to add this manually, which is painful with packages that use a lot of files.
But those should be minimal. With that P_PFM, could easily discover that there are replacement strings in a certain file and set them in the package.xml file.It might make sense to add a blanket replacement function to p_pfm, something like: $pfm->addGlobalReplacement('@ver@', 'package-info', 'version'); Otherwise, it works just fine with the existing addReplacement() method. Greg