Re: Template Proposal

On Thursday, November 8, 2001, at 04:02 PM, Richard Heyes wrote:

Andrei Zmievski wrote:

On Thu, 08 Nov 2001, Martin Jansen wrote:

That's exactly where to problems arise: The function names in Smarty don't correspond to the PEAR coding standards ;-). But maybe we can also find a solution for this.

Yeah, make an exception. :)

Why?

Why not? :) As long as they provide ample documentation to refer to, does it really matter what the functions are called? Unless they are simply too unclear and can be improved in that regard, I would leave them. If people have already been coding with the old function names, it could end up being an unreasonable or wasted investment of time to go through all their code and update things. I was hoping to PEAR-ize a bunch of my classes, but that would mean too much work just updating the code that relies on them. If some of the coding standards (ie. function naming conventions, tabs vs. spaces, where to place curly braces, etc.) were a little more compromising... well, I'm just not sure whether strict adherance benefits or detracts from productivity. I should apologize, I'm not trying to complain or spark a debate, I just tend to rant too much. ;) Lux

-- Richard Heyes "If you have any trouble sounding condescending, find a Unix user to show you how it's done." - Scott Adams -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net For additional commands, e-mail: pear-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net