Re: Why change require_once? A brief explanation of motives

From: Date: Wed, 18 Jul 2007 07:04:57 +0000
Subject: Re: Why change require_once? A brief explanation of motives
References: 1 2 3 4 5 6 7 8 9  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-47591@lists.php.net to get a copy of this message
How am I supposed to lazy load an the Exception implementation by just relying on require_once? depending on how you use Exceptions (control flow or in exceptional situations)
require_once 'MyPackage/Exception.php; throw new MyPackage_Exception_FileNotFound($thefile); the require_once goes at the start of the file (if the flow depends on it) or just before the call if it's really exceptional. So far the only justification that is currently not been explored for this change is "enables more flexibility" - Could you explain how it would enable that? and why that flexibility would be useful and commonly used. I can not see any amazing flexibility, only more problems. Regards Alan
regards, Lukas


« previous php.pear.dev (#47591) next »