Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18438
Return-Path: <helly@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 35134 invoked by uid 1010); 25 Aug 2005 18:49:23 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 35119 invoked from network); 25 Aug 2005 18:49:23 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Aug 2005 18:49:23 -0000
X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6
Received: from ([81.169.182.136:57059] helo=strato.aixcept.de)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 06/B2-28235-1B21E034 for <internals@lists.php.net>; Thu, 25 Aug 2005 14:49:21 -0400
Received: from [192.168.1.3] (dsl-082-083-226-059.arcor-ip.net [82.83.226.59])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by strato.aixcept.de (Postfix) with ESMTP id D467E35C384;
	Thu, 25 Aug 2005 21:10:02 +0200 (CEST)
Date: Thu, 25 Aug 2005 20:47:24 +0200
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <375106742.20050825204724@marcus-boerger.de>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>,
	Jan Borsodi <jb@ez.no>, Raymond Bosman <rb@ez.no>,
	Frederik Holljen <fh@ez.no>, Tobias Schlitt <ts@ez.no>
In-Reply-To: <Pine.LNX.4.62.0508251400150.10004@localhost>
References: <Pine.LNX.4.62.0508021457590.2808@localhost>
	<Pine.LNX.4.62.0508251400150.10004@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 Derick,

Thursday, August 25, 2005, 2:01:56 PM, you wrote:

> On Tue, 2 Aug 2005, Derick Rethans wrote:

>> we're finding some problems with property overloading (__get() and 
>> __set()). Here is an RFC describing what we'd like to see changed. 
>> Please comment on this.

> I updated the proposal:
> http://files.derickrethans.nl/property_overloading.html

> If nobody as any better idea on how to solve it I'd like to start 
> implementing it.

Instead of "__have_prop" can you make that "__has_prop" or "__exists" or
"__declared". "have" simply seems wrong thus (2). However that uses two
words which i don't like and so i cam to (3) and (4). Version (3) is better
than (4) because ArrayAccess also uses "exists".


Best regards,
 Marcus