Hi!
Just had such a problem myself a few weeks ago: a minor update
(IIRC was from 5.3.2 to 5.3.3) broke virtually all of my web applications
Out of curiosity - what exactly broke it? What change was it?
I got the strange feeling that php-devs don't care very much of long
term stability ;-p
* James Butler wrote:
> Enterprise (who-ever that is :-) now uses PHP and as such will
> want PHP to have some degree of uniformity with release cycles
> and feature addition/removal so that they can easily factor it
> in to their own deployment/upgrade plans etc.
Having worked for several lar
* Ferenc Kovacs wrote:
> You can't expect the users to switch to the new major version as soon as it
> comes out. They have to either migrate their codebase, and sadly they will
> wait(at least me and my collegues/friends do this) one or two micro/build
> version bump, usually the new major/major
Hi!
When I am inside the body of an autoloader function, am I allowed
to assume the invariant that the class passed to the autoloader function
does not exist? Last time I checked, PHP was still single-threaded,
Generally, yes, though nothing prevents somebody from calling the same
function e
Hello all, long time no see.
When I am inside the body of an autoloader function, am I allowed
to assume the invariant that the class passed to the autoloader function
does not exist? Last time I checked, PHP was still single-threaded,
so this invariant being broken would be quite suprising to me
