Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23328
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 84355 invoked by uid 1010); 13 May 2006 09:27:26 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 84340 invoked from network); 13 May 2006 09:27:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 13 May 2006 09:27:26 -0000
X-PHP-List-Original-Sender: helly@php.net
X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6
Received: from ([81.169.182.136:47520] helo=strato.aixcept.de)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 92/42-19568-D76A5644 for <internals@lists.php.net>; Sat, 13 May 2006 05:27:25 -0400
Received: from baumbart.mbo (dslb-084-063-053-215.pools.arcor-ip.net [84.63.53.215])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by strato.aixcept.de (Postfix) with ESMTP id A59BB35C1D1;
	Sat, 13 May 2006 11:27:21 +0200 (CEST)
Date: Sat, 13 May 2006 11:27:34 +0200
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <932738738.20060513112734@marcus-boerger.de>
To: Etienne Kneuss <colder@php.net>
Cc: Jason Garber <jason@ionzoft.com>, internals@lists.php.net
In-Reply-To: <44647B7A.2070301@php.net>
References: <785810036.20060511193536@ionzoft.com> <44647B7A.2070301@php.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] private, protected, readonly, public
From: helly@php.net (Marcus Boerger)

Hello Etienne,

Friday, May 12, 2006, 2:11:38 PM, you wrote:

> Hi,

> my 2c:

> 1) it shouldn't replace the visibility definition: we could also have
> protected readonly properties.

same here visibility and read/write control are two seperate things.

> 3) how would you check if the property if readonly ? Trying it could
> result to a Fatal error as you wanted. You would then need a
> isReadonly() method/function: the function call wouldn't be spared.

We could add this to reflection api easily.

Best regards,
 Marcus