Hey Bernhard, I see a few problems with the proposal:
1) If you're adding all of the ArrayAccess functions, what about all of the Iterator functions? How about other SPL aspects, like Countable, etc. 2) The use case can still be handled with an actual object which implements ArrayAccess and in a better practice scenario, unless I misunderstood what your code sample was implying. (if so, could you provide a complete, concrete example where it would be more advantageous to have these four additional accessor functions?) 3) Zero other languages that I am aware of implement anything more than get/set for accessors, the need for isset/unset is obvious for php because they are so heavily used. In fact, this document referenced in Dennis's original RFC shows 11 other languages with accessors, none of which have more than get/set. http://en.wikipedia.org/wiki/Property_%28programming%29 Lastly, it would probably delay this project another 6 months, perhaps it could be shelved for a version 2 of the accessors aspect? -Clint > -----Original Message----- > From: Bernhard Schussek [mailto:bschus...@gmail.com] > Sent: Friday, October 12, 2012 3:07 AM > To: Clint Priest > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] [PHP-DEV [RFC] Property Accessors v1.2 > > Hi Clint, > > I would like to urge you again to consider implementing the array access > methods. Without that, this very neat feature becomes > essentially unusable for modelling one-to-many, many-to-one and many-to-many > object relations, as I tried to explain in the previous > topic. > > Objects and relations between them are the most primitive building block of > OO design, so I regard this as highly important. > > Thanks, > Bernhard
