Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23528 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23922 invoked by uid 1010); 17 May 2006 10:30:49 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 23907 invoked from network); 17 May 2006 10:30:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2006 10:30:49 -0000 X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:45493] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 93/52-19568-85BFA644 for ; Wed, 17 May 2006 06:30:49 -0400 Received: (qmail 13459 invoked from network); 17 May 2006 10:30:35 -0000 Received: from shire.zend.office (10.1.2.160) by internal.zend.office with SMTP; 17 May 2006 10:30:35 -0000 Date: Wed, 17 May 2006 13:30:35 +0300 (IDT) X-X-Sender: frodo@shire.zend.office To: Jason Garber cc: internals@lists.php.net In-Reply-To: <1014418169.20060516181322@ionzoft.com> Message-ID: References: <785810036.20060511193536@ionzoft.com> <44647B7A.2070301@php.net> <932738738.20060513112734@marcus-boerger.de> <837405862.20060513223403@ionzoft.com> <36828701.20060514110529@marcus-boerger.de> <31269879.20060514221212@marcus-boerger.de> <1327845846.20060514222154@marcus-boerger.de> <1562034641.20060516203354@marcus-boerger.de> <7.0.1.0.2.20060516235201.090f10a8@zend.com> <7.0.1.0.2.20060516142654.02c78380@zend.com> <596643859.20060516233753@marcus-boerger.de> <7.0.1.0.2.20060516144030.039abe98@zend.com> <1531743211.20060516234945@marcus-boerger.de> <1014418169.20060516181322@ionzoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] private, protected, readonly, public From: stas@zend.com (Stanislav Malyshev) JG>> private readable $abc; JG>> - doesn't make sense. JG>> JG>> protected readable $abc; JG>> - sub-class can read, not write JG>> - not visible outside class JG>> JG>> public readable $abc; JG>> - sub-class can read, and write JG>> - outside class can read, not write For me such setup seems quite weird - why adding "readable" keyword to "public $x" ort "protected $x" makes it read-only? It's not exactly what word "readable" means - it means you can read, not you can not write. I'd say adding "readable" means everybody could read it, while writing still restricted by access modifier, so readable private means only owner can write, readable protected means owner and descendants can write and readable public is just public. This would make more sense - if we decide readable should be a modifier, of course. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115