Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23561 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37215 invoked by uid 1010); 17 May 2006 23:48:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 37200 invoked from network); 17 May 2006 23:48:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2006 23:48:28 -0000 X-PHP-List-Original-Sender: jared@intuitivefuture.com X-Host-Fingerprint: 209.59.182.2 unknown Linux 2.4/2.6 Received: from ([209.59.182.2:57134] helo=amplex.webserversystems.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1E/99-19568-C46BB644 for ; Wed, 17 May 2006 19:48:28 -0400 Received: from whitecockade.com ([64.142.12.177] helo=[192.168.0.9]) by amplex.webserversystems.com with esmtp (Exim 4.52) id 1FgVke-0004li-PR for internals@lists.php.net; Wed, 17 May 2006 19:48:24 -0400 Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: 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> <1677590447.20060517002135@marcus-boerger.de> <446A5B52.9060001@cschneid.com> <27079878.20060516191743@ionzoft.com> <446A601A.8010205@vocalspace.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <7492F175-8124-4518-9AB2-5FA7A2603483@intuitivefuture.com> Content-Transfer-Encoding: 7bit Date: Wed, 17 May 2006 14:39:58 -0700 To: internals@lists.php.net X-Mailer: Apple Mail (2.749.3) X-Antivirus-Scanner: This message has been scanned by ClamAV. X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - amplex.webserversystems.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - intuitivefuture.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [PHP-DEV] private, protected, readonly, public From: jared@intuitivefuture.com (Jared White) On May 17, 2006, at 2:25 PM, Stanislav Malyshev wrote: > This would be, however, yet another level of complexity added to the > language... OOP is already a level of complexity. If you're going to have OOP in the language, it needs to support at least the standard needs that developers have when using OOP. PHP has properties, good. PHP has virtual properties via __get and __set...good. Now, if PHP is not going to have some kind of accessor method standard, I can live with that -- however, being able to control read/write settings for properties seems highly standard. Saying it is too confusing for newbies is basically saying OOP is too confusing for newbies. If a newbie learns what a property is, then at the same time they can discover that you can set read/write access for properties. You can set read/write access for files, right? So you can for properties. Makes sense to me. That being said, I think the current syntax options being discussed are somewhat cumbersome. "readable" doesn't really sit well with me. I wish I were clever enough to come up with an alternative, but I ain't. :) Take care, Jared