Re: Re: coding standards: Header Comment Blocks

Hi Greg Beaver! 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. :) > um, might want to read docs before posting. :) > > http://pear.php.net/manual/en/package.pear.pear-packagefilemanager.pear-packagefilemanager.addreplacement.php Doh! Got me! ;) So, I guess it would be a good idea having this replacement set by default in every package.xml. Or? Changing the coding standards to have a real docblock instead of the vi stuff sounds even good to me. I'm not sure, if we can simply change that, or minimally should have a kind of "pseudo-vote" here on the list, therefore, I'd like to have a little new thread, explaining what we wanna do and having people replying with their +/-1. Anyo objections to that? Regards, Toby -- Tobias Schlitt a passion for php http://www.schlitt.info