Re: autoload (was: Comments on bugs marked bogus)
| From: | Lukas Smith | Date: | Wed, 27 Jul 2005 09:54:41 +0000 |
| Subject: | Re: autoload (was: Comments on bugs marked bogus) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38964@lists.php.net to get a copy of this message | ||
Alan Knowles wrote:
On Wed, 2005-07-27 at 09:13 +0200, Bertrand Mansion wrote:I disagree. A quick look into my framework revealed to me that I could probably start using __autoload() today with little issues. Though at that point I would probably also want to use interceptors to create the entire object instance on demand as well. $this->mdb2 somehow magically creates the instance on demand, and there I run into case issues again so it would have to be $this->MDB2 and where does the configuration come from in that case? So maybe I will have to hardcode the supported packages into my interceptor method anyways. If this posting doesnt make sense at first reading (or at all), then the reason is that I am thinking aloud with no real conclusion .. regards, LukasAlan Knowles wrote:quite agree, using __autoload is like driving without headlights at night.. If you are lucky it might work.. - but as long as I'm in a different country, you are free to do it ;)I think autoload will be fixed to allow failure - It's a known bug of the autoload implementation ....The bug is not that it should allow failure. The bug is more that is_a() shouldn't IMO call __autoload().