ID: 27929 Updated by: [EMAIL PROTECTED] Reported By: juwe at clasennet dot de -Status: Open +Status: Bogus Bug Type: Feature/Change Request Operating System: Does not matter PHP Version: 5CVS-2004-04-09 (dev) New Comment:
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php ArrayObject encapsulates the array and ArrayIterator depends on that encapsulation. For the moment i do not see any reason to change that behavior. Previous Comments: ------------------------------------------------------------------------ [2004-04-09 07:02:47] juwe at clasennet dot de Description: ------------ Hello, when I just tested the SPL I found a necessity to create an iterator for an existing array. Since ArrayIterator::__construct() is currently declared private, I've first had to create a completely unnecessary (well, at least from my point of view) instance of ArrayObject, just to produce an Iterator with ArrayObject::getInstance(). Could someone please have a look at that one and decide if it is possible to allow public access on ArrayIterators without the necessety to create foreign objects in before? I know this is just a minor issue at the moment, but I'd prefer such things beeing changed, before they are used in a productive environment. Thanks Jens Clasen P.S.: Please excuse my bad english - I am no native speaker. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27929&edit=1
