Re: Re: Final RFC for Net_SMPP/Net_SMPP_Client

Ian Eure wrote:

On Tuesday 19 July 2005 03:06 pm, Pierre-Alain Joye wrote:

On Tue, 19 Jul 2005 14:58:09 -0700

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.

As simple line in the doc, such as "All operation names follow the studlyCaps notation. As such, Net_SMPP_Command_SubmitSm represents the 'submit_sm' command." Obviously there were some mistakes in older packages. However, most packages follow the same rule, which makes it convenient to the PEAR users. Not too much wondering around there. As far as PHP_Compat is concerned, the file name matches the function declared inside of it, which MUST be the same as PHP declare them for obvious reasons. -Philippe