Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23326 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62886 invoked by uid 1010); 12 May 2006 23:43:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 62871 invoked from network); 12 May 2006 23:43:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 May 2006 23:43:44 -0000 X-PHP-List-Original-Sender: bfoz@bfoz.net X-Host-Fingerprint: 204.127.192.83 rwcrmhc13.comcast.net NetCache Data OnTap 5.x Received: from ([204.127.192.83:48613] helo=rwcrmhc13.comcast.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1E/D8-19568-0BD15644 for ; Fri, 12 May 2006 19:43:44 -0400 Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (rwcrmhc13) with ESMTP id <20060512234340m1300f95nse>; Fri, 12 May 2006 23:43:40 +0000 Message-ID: <44651DAA.4020209@bfoz.net> Date: Fri, 12 May 2006 16:43:38 -0700 User-Agent: Thunderbird 1.5.0.2 (X11/20060507) MIME-Version: 1.0 To: Jason Garber CC: internals@lists.php.net References: <785810036.20060511193536@ionzoft.com> In-Reply-To: <785810036.20060511193536@ionzoft.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] private, protected, readonly, public From: bfoz@bfoz.net (Brandon Fosdick) Jason Garber wrote: > Would it be possible to create a new object property attribute: > readonly Why not make it a little more generic? Say, make readonly an attribute that applies to the ppp tags as opposed to making it a new access class. Eg. if a member is 'public readonly' then it's read/write for private and protected, but read-only in a public context. Similarly, 'protected readonly' is read/write in a private context, read-only in protected and not visible in public. That would make 'private readonly' read-only for private methods, and not visible to anything else, which is probably only useful for properties generated by extensions. Or is this what you're proposing and I'm just being dense?