News for hackers. Stuff that matters.
Re:What PHP 5.5 might look like by conradfr on Thursday July 12, 2012 @09:20AM (#4234328)
I, for one, never understood why there was no "default" keyword available, but the python example is great as well.

About the rest of the article :

- the modified empty() is nice, while I still think this function accepts to much thing as empty, or at least should be more flexible.

Getter/setter : finally. Now I don't get why there is no readonly keyword which would put the variable as readonly only for the class' outer world.

Re:What PHP 5.5 might look like by shakesbeard on Thursday July 12, 2012 @09:57AM (#4234491)
The article clearly states that there are more features like a read-only keyword.

https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented

Re:What PHP 5.5 might look like by jasonlotito on Thursday July 12, 2012 @10:06AM (#4234537)
That's not what he's referring to. He's specifically referring to a read-only that only affects external classes. So, the object itself could write to that field, but nothing else could.
Re:What PHP 5.5 might look like by shakesbeard on Thursday July 12, 2012 @10:17AM (#4234593)
You can set the visibility of both the properties and the getters/setters.

    class Foo {
        private $fuzz;
        
        protected $Bar {
            get { return $this->fuzz; }
            private set { $this->fuzz = $value; }
        }
    }
Re:What PHP 5.5 might look like by jasonlotito on Thursday July 12, 2012 @10:20AM (#4234605)
Yes. I understand that.

My point was just that he specifically wanted a read-only.