Re: private, protected, readonly, public

From: Date: Tue, 16 May 2006 23:28:26 +0000
Subject: Re: private, protected, readonly, public
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Jason Garber wrote:
CS> Does anyone apart from me wonder why we need to bloat the language for CS> an obscure feature like this? Please take a step back, take a deep CS> breath, count to 10 and that's *really* what the PHP community has been CS> waiting for. Please consider that not everyone does the same things with PHP that you do - you apparently haven't run into the need for it. That's okay, but others have.
I'm not familiar with this OOP concept from any other language. Perhaps it exists, but if it doesn't, is there a reason why? If you add a language construct like 'readable' or 'readonly' wouldn't that almost begin to require the need for reflection functions to go along with it: is_readable($object, $key) Or something like that? Dante

Thread (92 messages)

« previous php.internals (#23491) next »