[wp-trac] [WordPress Trac] #30891: Unchecked property overloading is detrimental to OOP.

[WordPress Trac]

#30891: Unchecked property overloading is detrimental to OOP.
--------------------------+------------------------------
 Reporter:  aercolino     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  4.0
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by jdgrimes):

 Replying to [comment:2 aercolino]:
 > In my suggested fix, legacy properties and methods are all the public
 members of each class before unchecked overloading was introduced into
 that class. Deprecation notices occurring when legacy non-public members
 are accessed from outside the hierarchy is a nice-to-have feature for
 synchronizing real usage with stated code and documentation along time,
 '''however''' that's not the issue I'm referring to here. Even without
 such notices, i.e. even allowing public access to legacy members forever,
 unchecked overloading should be fixed.

 I agree—that's why I said maybe it could be a follow up to this. :-)

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30891#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform