Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6173
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3FCE7F77.8010703@leetspeak.org>
Date: Thu, 04 Dec 2003 01:27:35 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030924 Thunderbird/0.3
MIME-Version: 1.0
To:  internals@lists.php.net
References: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1> <20031203221037.GA1828@gjat.josefine.at> <3FCE651E.5020308@leetspeak.org> <200312040102.34295.msopacua@php.net>
In-Reply-To: <200312040102.34295.msopacua@php.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] StudlyCaps
From: cm@leetspeak.org (Michael Walter)

Melvyn Sopacua wrote:
> 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.
Ah, I understand. Never got into former problems as I prefix my 
functions/classes with a package prefix. The latter point is 
interesting. Although it's true, I think you're just "moving" the 
problem into user-space, as it's an inherit "problem" of the language 
(no parametric polymorphism, no "non-virtual" calls, in c++ 
terminology). Like, if you have that 3rd party PHP library, and you 
inherit from it, you might as well run into problems if it uses 
studlyCaps. It definately removes the problem for built-in php 
functionality, though, I completely agree on that.

Cheers,
Michael