On 23 August 2014 01:56, Brian Wolff <bawolff(a)gmail.com> wrote:
The most major objection I would have, is that the
code would make all
private/protected properties accessible, not just the recently
deprecated. Otherwise the code kind of seems like a lesser evil.
I thought about introducing arrays of allowed variables for that case,
but decided against it.
Currently there should be no code in existence that accesses
previously private variables.
If somebody now starts to access private variables through this
mechanism that were not
accessible before, it is their own fault. They would have to
specifically find the __get/__set
methods and decide to use them in spite of them being clearly marked
as deprecated and
in the full knowledge of them being removed in 12 months latest.