Re: StudlyCaps
| From: | Melvyn Sopacua | Date: | Thu, 04 Dec 2003 00:02:27 +0000 |
| Subject: | Re: StudlyCaps | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-6170@lists.php.net to get a copy of this message | ||
On Wednesday 03 December 2003 23:35, Michael Walter wrote:
> Markus Fischer wrote:
> > [...]
> >
> > I like the initial argument brought up by Mr. Wendel, namely to
> > easily differentiate between PHP method calls and userland written
> > method calls.
> >
> > - Markus (and his cow)
>
> How is this an advantage?
FWIW: it's not only an advantage, it's the reason I strive to use studlyCaps
in my userland functions - because they will never clash on the next php
upgrade (and the whole image* functions is a pain in the butt in that area).
What happens if a php provided object I extended chooses to implement the
same method and call it internally, expecting different results? Upgrading is
enough hasstle.
My 2c + a cow.
--
Melvyn
=======================================================
FreeBSD sarevok.idg.nl 5.2-BETA FreeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 CET
2003 root@sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOACPI
i386
=======================================================