This is what I'm saying.
But the current grammar lacks within the use of const and final!
And that's what it's all about - that's my point. ;)
Lukas Kahwe Smith schrieb:
On 13.02.2008, at 21:52, Andi Gutmans wrote:
Guys,
I think we are over-engineering and over-complicating here. Reminds me
a patch in may 2006 (ze2-readable_properties-20060516.diff.txt)
that implements the new visibility promulgate (which i thought of as a funny
solution to public read).
marcus
Wednesday, February 13, 2008, 11:18:17 AM, you wrote:
Em Qua, 2008-02-13 às 10:59 +0100, Sebastian Schneider escreve
nnot be changed in the context of the
object.
However you could implement a method for this, e.g. get_status(); which then
returns an array. But the final keyword would be more comfortable....
"Sebastian Schneider" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECT
Sebastian Bergmann schrieb:
Sebastian Schneider schrieb:
public static final $bar = "foobar's world";
We have the const keyword for that.
But doesn't work with arrays, e.g.
public class Result {
const DECISION_PERMIT = 0;
const DECISION_DENY
Hey you guys,
it would be very helpful to be able using the keyword _final_ not only
for classes and methods but for variables as well - such as
to prevent changes from outside though at least publicly readable.
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscri
