Re: Re: Final RFC for Net_SMPP/Net_SMPP_Client

On Tuesday 19 July 2005 03:06 pm, Pierre-Alain Joye wrote: > On Tue, 19 Jul 2005 14:58:09 -0700 > > ieure@php.net (Ian Eure) wrote: > > On Tuesday 19 July 2005 02:18 pm, Pierre-Alain Joye wrote: > > > http://pear.php.net/manual/en/standards.naming.php > > > "The PEAR class hierarchy is also reflected in the class name, > > > each level of the hierarchy separated with a single underscore." > > > > > > Can it be more clear? > > > > Yes, it can. "PEAR hierarchy" is not defined, and it's not clear > > if that means "the category/subcategory structure" or "absolutely > > every file in a PEAR installation." > > PEAR folder hierarchy, please do not with words :) > Well, that's not explicitly stated, and there are enough packages that don't follow it that it's not clear. > > So you advocate making a project harder to use because it's > > internal structure (which should never be used directly) doesn't > > match the PEAR conventions? That seems like a pretty bad > > trade-off to me. > > In what is it harder? > It's harder because you need to read the SMPP specification, then read additional documentation about how Net_SMPP works relative to that document. If Net_SMPP follows the spec closely, you only have to learn a few functions, instead of relearning part of the actual spec. > > Furthermore, I note that you are the lead developer of both > > HTML_Template_IT and XML_XSLT_Wrapper. I fail to see how you can > > argue that this is bad when I do it, yet perfectly fine when you > > do. > > Both were there before we defined these rules. They are still like > so for obvious BC reasons. > Your statement is demonstrably false. According to the CVS logs for the chapter of the manual you reference, that text has been in place since Sep 30th, 2002. However, it was obviously an import of a preexisting document. The Internet Archive's Wayback Machine shows that text was there as early as Feb. 25th, 2002. Both XML_XSLT_Wrapper and HTML_Template_IT post-date that specification by a good 7-8 months. So I ask again: why does the rule apply to me and not to you? You also completely ignore my arguments regarding I18Nv2 and PHP_Compat. Both packages postdate that section of the manual by a good two years, and both use underscores to ease compatibility with other specifications. This is the exact reason I wish to have files with underscores in my package.

Attachment: [application/pgp-signature]