Hi,
[quote from off-list:]
> I am in way over my head and would not do a good job
> fixing these (or have the time), care to take a crack at it?
Ok, I'll do that tomorrow morning.
> I wonder if the problem is that
> spl_autoload_register should not just be checking to see if zcallable is
> IS_OB
Christian Seiler wrote:
> Hi Greg,
>
>
>> (I meant commit when I said patch, sorry :)
>>
>> http://news.php.net/php.cvs/58696
>> and
>> http://news.php.net/php.cvs/58697
>>
>
> Thanks, looks fine to me. However, I noticed that closures don't work
> with spl_autoload_unregister() and spl_aut
Hi Greg,
> (I meant commit when I said patch, sorry :)
>
> http://news.php.net/php.cvs/58696
> and
> http://news.php.net/php.cvs/58697
Thanks, looks fine to me. However, I noticed that closures don't work
with spl_autoload_unregister() and spl_autoload_functions(). Also,
classes that define __in
Christian Seiler wrote:
> Hi Greg,
>
>> I can do it if someone can answer this question: how do closures
>> uniquely identify themselves? spl_autoload_register is mistakenly
>> treating all closures as if they were a single copy of the static method
>> "Closure::__invoke", and so only the first r
Hi Greg,
> I can do it if someone can answer this question: how do closures
> uniquely identify themselves? spl_autoload_register is mistakenly
> treating all closures as if they were a single copy of the static method
> "Closure::__invoke", and so only the first registered closure is ever
> call
Hi,
I didn't mark http://bugs.php.net/48541 as critical because it is not a
critical bug, but it is critical that this thing be fixed in PHP 5.3.
I can do it if someone can answer this question: how do closures
uniquely identify themselves? spl_autoload_register is mistakenly
treating all closur
