Bug #55300 [Opn->Asn]: \DirectoryIterator, parent::__construct() and \LogicException

Edit report at https://bugs.php.net/bug.php?id=55300&edit=1 ID: 55300 Updated by: felipe@php.net Reported by: frederic dot hardy at mageekbox dot net Summary: \DirectoryIterator, parent::__construct() and \LogicException -Status: Open +Status: Assigned Type: Bug Package: SPL related Operating System: Linux PHP Version: 5.4.0alpha2 -Assigned To: +Assigned To: cataphract Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2011-08-04 06:56:27] frederic dot hardy at mageekbox dot net This BC break is a problem with the symfony 2 framework. All command throw this exception : [LogicException] In the constructor of Symfony\Component\Finder\SplFileInfo, parent::__construct() must be called and its exceptions cannot be cleared ------------------------------------------------------------------------ [2011-07-28 08:44:49] pajoye@php.net Thing is that it is a bc break, whether it was well designed in the 1st place or not is sadly not relevant here. Is there any way to restore this behavior without bc breaks? ------------------------------------------------------------------------ [2011-07-28 08:29:38] cataphract@php.net Why can't you use a user stream wrapper then? Maybe DirectoryIterator should be an interface, but it isn't. ------------------------------------------------------------------------ [2011-07-28 07:27:19] frederic dot hardy at mageekbox dot net This bug seems to be related to #54384. And i want to do this to mock a \DirectoryIterator instance, to "simulate" a directory on the file system. ------------------------------------------------------------------------ [2011-07-27 23:30:06] cataphract@php.net If you don't call the parent constructor, the class has no functionality. Why would you want to do this? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=55300 -- Edit this bug report at https://bugs.php.net/bug.php?id=55300&edit=1