Re: Re: coding standards: Header Comment Blocks

Tobias Schlitt wrote:

Hi Tomas V.V.Cox! You wrote:

Can't be that hard to implement that in PEAR_PackageFileManager, can it?

It's not hard at all, just read the contents of each file, scan for /@(.*)@/ and build the xml. Any of the presents in this lists can have it done in no more than 30 mins ;)

I'd do that even more simply. Create a new method: addReplacement($from, $to, $type='package-info#) done. :) More flexible and I guess more feasible, because the file scan does not know which "type" to set and what the replacement should be.

That's why my first post said: "replacements should need some regulations unless Greg learned black magic" :-). If we all agree that for example @release-version@ would be the correct "tag" for the package release version replacement, you won't need to call your method for each file and each replacement. Tomas V.V.Cox