Re: Re: cvs: php-src /tests/classes array_access_001.phpt array_access_002.phpt array_access_003.phpt array_access_004.phpt ZendEngine2
zend_execute.c zend_interfaces.c zend_interfaces.h zend_object_handlers.c zend_operators.c zend_operators.h

Well, I can live with any of those names :) Didn't realize either, that it would be that much of a deal to rename an interface ;) I wasn't talking about is_a(), though, but of the general concept of using inheritance for modelling "is a" relationships, hence the name recommendation. Although, as said, I suppose ArrayAccess is okay as you could say "implements". Marcus Boerger wrote:

Hello Michael, Tuesday, November 25, 2003, 6:57:30 AM, you wrote:

And how about calling it Indexable, or something that can be used in a "is a" sentence? As in, you could say "MyArray is an Indexable", but "MyArray is an ArrayAccess" sounds just wrong ;)

is_a() is deprecated use instanceof now and that works with any class name. (We are not SQL here) Besides that the patch took about half a year of writing, discussion and planning and i was hoping we finally chose good names. Can you live with them?