Hello Alexey, that is probably but i wouldn't like it. I think we are going to make it to complex, tooooo Java like. Keep it simple. The only bad thing is a bit of a slowdown - eventually - where not loading all classes always by include isn't slower anyway. That said what we need to solve is the problem of emitting usefull errors. So maybe the idea of knowing whether the class is required or optional is the key here. Because once we have that we can already do what we need. The one resplonsible handler simply emits the error and we're done. If it doesn't know whether the class is necessary or not we cannot do so.
marcus Saturday, October 6, 2007, 12:02:15 PM, you wrote: > On 10/6/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: >> >> Then loader should be able to tell the engine that it shouldn't try >> another handler. > I am not sure, that is a good idea. > Probably, it would be better to allow registering different autoload > functions per-namespace basis? > I think that can be done by extending spl_autoload_* family of > functions and leaving autoload_register() as low-levelish as it is now > -- > Alexey Zakhlestin > http://blog.milkfarmsoft.com/ Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
