Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18481
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 26 Aug 2005 20:32:30 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <273979752.20050826203230@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>
Cc: Edin Kadribasic <edink@emini.dk>,
	Derick Rethans <derick@php.net>,
	Christian Schneider <cschneid@cschneid.com>,
	PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <6.2.3.4.2.20050825182507.064da170@localhost>
References: <Pine.LNX.4.62.0508021457590.2808@localhost>
	<Pine.LNX.4.62.0508251400150.10004@localhost> <430DBD80.6090804@cschneid.com>
	<Pine.LNX.4.62.0508251448160.10004@localhost> <430DC0DC.4060506@emini.dk>
	<6.2.3.4.2.20050825182507.064da170@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Property Overloading RFC
From: helly@php.net (Marcus Boerger)

Hello Andi,

Friday, August 26, 2005, 3:39:08 AM, you wrote:

> At 06:00 AM 8/25/2005, Edin Kadribasic wrote:
>>Derick Rethans wrote:
>> > And how can you possibly argue that this more complex than all the other
>> > OO crap that people are suggesting here....
>>
>>I belive that we should do our best to filter out this storm of OO
>>feature requests. People want to make PHP look like some other OO
>>languages for no good reason other that they're familiar with it or that
>>their CS teacher thought they were cool.

> I completely agree.
> This very much bloats the language syntax and would be mainly there 
> for the sake of OO fanatics. Guys, seriously, this kind of stuff and 
> a lot of the other OO proposals I've heard here lately are going to 
> lead to PHP going down the drain. Derick, the fact that you say it's 
> not worse than "other OO crap that people are suggesting here...." 
> just means that it's also good to leave the other crap out of PHP.
> Sometimes I really wished people who really need this kind of crap go 
> and download Python & Smalltalk, instead of killing PHP's benefits. 
> There is no language that does everything, and I'd like to keep PHP 
> good at what it does best. People who aren't content with PHP not 
> being a master piece in object oriented really should look elsewhere. 
> I'll be happy to hear back from them regarding development time, 
> ease-of-use and training period for developers.

> I don't see why the __get/__set/__isset/__unset methods themselves 
> can't check if the property exists and throw an exception if it 
> doesn't. I always do that in all my examples...

Interesting, How do you do that? There is no __isset or __unset.

> As far as 
> documentation is concerned, you'll usually have a nice array in the 
> beginning of the class declaration which is pretty verbose, if that's 
> not good enough people can use phpDoc (or we can enhance phpDoc). If 
> you strongly feel that something like _have_prop() is needed despite 
> exceptions doing the job, it's something that could be considered but 
> I'm not convinced it's needed.

> Andi




Best regards,
 Marcus