Stanislav Malyshev wrote:
Hi!
This fixes the logic problem, and re-introduces the performance
slowdown for internal classes. FORTUNATELY there is a simple
solution to this, which is to "use" all global classes:
The thing is since it'd work without "use", most users would do it
that way and
Lukas Kahwe Smith schreef:
On 10.07.2008, at 14:43, Richard Krehbiel wrote:
Here's the big part: I was thinking that a semantic change to persistent
sockets might make it easier for scripts to work "correctly" without
bothering them too much. The change is this: If a script doesn't
"fclose
Hi Ryan,
Am Freitag, den 11.07.2008, 08:11 -0500 schrieb Ryan Panning:
> Was static member overloading added in PHP 5.3? I noticed that static
> method overloading was (__callStatic). The two would complement each
> other and it just seems natural to add these as well. I did notice
> that they
Was static member overloading added in PHP 5.3? I noticed that static
method overloading was (__callStatic). The two would complement each
other and it just seems natural to add these as well. I did notice that
they are apart of the "static-class" RFC and a bug report, but it would
be nice to s
Hello all,
Over the last week we have collected todo/wishlist items for PHP 5.3
[1]. We have tried to get in contact with all the known stakeholders
and we have we have gotten enough information from you all that our
release plan will be more than tentative, but you never know and
common
On 10.07.2008, at 14:43, Richard Krehbiel wrote:
Here's the big part: I was thinking that a semantic change to
persistent
sockets might make it easier for scripts to work "correctly" without
bothering them too much. The change is this: If a script doesn't
"fclose"
it's "pfsockopen"ed soc
