Lukas Kahwe Smith wrote: > > On 16.10.2008, at 17:37, Stanislav Malyshev wrote: > >> B. There's a huge problem with this proposal which you seem >> consistently to ignore despite all my attempts to explain it. Failed >> autoload on each call is BAD. Very bad. It is not cacheable, it leads >> to multiple disk accesses and it is absolutely undetectable to the >> PHP user without the use of special tools. So making all existing >> code contain this performance bomb unless you rewrite it is very bad. >> It's better to have this code fail and provide simple script to fix >> it in automatic fashion. The fix you propose - writing use's - is not >> enough because as you noted later inertia would make users not to use >> this code and thus have huge performance hit - which most of them >> even wouldn't know where it came from. > > first up i am a bit irritated by the use of the term "internal class", > i guess you both mean to say "class in the global namespaces"? no, we are talking about classes built into PHP such as Exception or ArrayObject, not userspace classes without namespace.
Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
