#48667 [Asn->Csd]: "could not implement" - NOT redefining functions

ID: 48667 Updated by: colder@php.net Reported By: uramihsayibok at gmail dot com -Status: Assigned +Status: Closed Bug Type: SPL related Operating System: Windows XP PHP Version: 5.2.10 Assigned To: colder New Comment: This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. Both orders are now restricted. The problem is not that they do share any function, but they both overwrite the internal get_iterator handler used by foreach, for instance. Previous Comments: ------------------------------------------------------------------------ [2010-02-01 13:45:57] svn@php.net Automatic comment from SVN on behalf of colder Revision: http://svn.php.net/viewvc/?view=revision&revision=294304 Log: Fix #48667 (Implementing Iterator and IteratorAggregate is now restricted in both orders) ------------------------------------------------------------------------ [2009-08-26 12:29:11] admin at somesite dot de When i set display_errors to on and display_startup_errors to on i even get an error message window displaying the same error. according to the taskmanager, this window is created by csrss.exe . i use Windows XP SP2 with xampp + PHP5.3 ------------------------------------------------------------------------ [2009-08-25 07:27:26] sjoerd@php.net Reproducable and strange. Error is also not very descriptive. ------------------------------------------------------------------------ [2009-06-23 22:14:17] uramihsayibok at gmail dot com Description: ------------ When trying to make a class that implements IteratorAggregate and SPL's SeekableIterator the order of the interfaces in the list matters. One order (IA first SI second) works while the other (SI first IA second) produces a fatal error in Unknown. THESE TWO INTERFACES ARE SEPARATE AND DISTINCT - NO FUNCTIONS IN COMMON! Traversable -> Iterator -> SeekableIterator (seek,current,next,key,valid,rewind) Traversable -> IteratorAggregate (getIterator) I haven't been able to reproduce this with user-defined interfaces and I haven't gone looking to see if this happens with any other built-in interfaces. Something to do with that fact that they redefine how iteration on a class works? Reproduce code: --------------- #1 (works) abstract class Foo1 implements IteratorAggregate, SeekableIterator {} #2 (does not work) abstract class Foo2 implements SeekableIterator, IteratorAggregate {} Expected result: ---------------- #1 and #2 should both work or both not work. In this case, work, since neither have any functions in common to redefine. Actual result: -------------- #1 - okay #2 - "Fatal error: Class Foo2 could not implement interface IteratorAggregate in Unknown on line 0" ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=48667&edit=1