RE: [PEAR-DEV] Template Proposal
| From: | Richard Heyes | Date: | Thu, 08 Nov 2001 23:23:51 +0000 |
| Subject: | RE: [PEAR-DEV] Template Proposal | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2704@lists.php.net to get a copy of this message | ||
Lux wrote:
> 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? :)
Because a coding standard is just that, a standard. Andrei commented
previously that there are so many standards you can choose to support, well
that's wrong. There are usually a single set of standards, and the thing
that varies is the implementations of those standards. Browsers are of
course the classic example. Making exceptions to the rule are one way of how
these various implementations come about.
> 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 think having all the PEAR code look as similar as possible is a great
thing and makes reading the code much easier.
> I should apologize, I'm not trying to complain or spark a debate, I just
> tend to rant too much. ;)
Debate is what we're here for. :)
--
Richard Heyes
"If you have any trouble sounding condescending,
find a Unix user to show you how it's done." - Scott Adams