Stas, go back a few "revisions" of the RFC and you'll see there used to be automatically implemented accessors which were voted out. The current RFC does not reflect the current "fork" of the code, it did before I modified it with the consensus from around 10/12 before Nikita brought up some more thoughts on the subject.
I believe the general idea of the changes is documented at the bottom of the document in the change list, but you're free to go back to previous versions of the RFC. > -----Original Message----- > From: Stas Malyshev [mailto:smalys...@sugarcrm.com] > Sent: Tuesday, October 16, 2012 5:48 AM > To: Jazzer Dane > Cc: Clint Priest; internals@lists.php.net > Subject: Re: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 > > Hi! > > > Stas, the proposed "solution" thus far is to make the getter or setter > > final and private and not have a body. This would naturally throw an > > exception if it was accessed from anywhere but the class it was defined. > > The class it was defined in has to remember that it is virtually a > > read/write only accessor. > > What you mean by "not have a body" - is there special syntax for body-less > methods introduced? Then it should be in the RFC. How > it is implemented - what exactly is stored in the function table then? > > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
