On Sun, Sep 21, 2003 at 09:10:16AM -0700, Raquel Rice wrote:
:
: On Wed, 17 Sep 2003 21:22:36 +1000
: Justin French <[EMAIL PROTECTED]> wrote:
:
: > I posted a similar topic a few months back. I guess the answer is
: > that the collaborative nature of open source, and the fact that
: > PHP has g
Am Mit, 2003-09-17 um 14.26 schrieb [EMAIL PROTECTED]:
> In practice, I find that all my code is wrapped up in custom functions and
> objects anyway - I name those quite carefully to avoid confusing myself and
> others, but don't need to worry too much about the naming conventions of the
> functi
The English language can be just as confusing at times, and is full of
exceptions to rules - people just get used to them. The same can apply to a
programming language. I'm not of why PHP's naming conventions are like this,
but I can only assume it's to do with the way the language has evolved,
per
I posted a similar topic a few months back. I guess the answer is that
the collaborative nature of open source, and the fact that PHP has
grown from very humble beginnings has meant that naming standards and
conventions are a little lacking.
It would've been nice if these issues were rectified
4 matches
Mail list logo