[RFC] Property Accessors v1.2 : Interfaces

I'm opening up several new threads to get discussion going on the remaining "being debated" categories referenced in this 1.1 -> 1.2 change spec: https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented/change-requests ------------------------------------------------------------------------ v1.1 fully allows accessors to be defined in interfaces and requires that those accessors be defined in implementing classes. Some people have suggested that a property defined by the class should also satisfy the requirement. *Arguments For* * From the outside observer of an interface, a class which defines a property has satisfied the requirement, because an interface only defines what must be allowed, not what cannot be done. *Arguments Against* * Additional overhead on interface checking, would only be allowed for a non-asymmetrical accessor * Would give userland developers the ability to write poor code as properties are non-observable (object would not know its property was changed) ------------------------------------------------------------------------ Thoughts? -- -Clint