Re: Apache2 SAPI behaviour regarding PATH_TRANSLATED

From: Date: Sun, 18 May 2003 16:02:19 +0000
Subject: Re: Apache2 SAPI behaviour regarding PATH_TRANSLATED
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-1679@lists.php.net to get a copy of this message
Sascha Schumann <sascha@schumann.cx> wrote: > > No more ini magics please. IMO we'd be better off preserving the bad-old > > convention for 4.3, and just bringing the correct implementation into 5.0 > > with some notes. > > We should try to mitigate PHP's perception of being hard to > upgrade due to devastating BC issues. Because of this, > sites frequently run 1-3 year old PHP versions with all their > bugs and holes. As such, it is essential to provide support > for legacy applications even in new PHP releases. Using inis > for that is a compromise between achieving that and doing the > Right Thing from the developer's perspective. Right, but it's also the case that adding more ini entries sorely for certain backwards compatibilities could make it harder for us to write portable scripts and could definitely generate a disgusting number of bogus PR's as in the case of register_globals. Therefore any attempts of such mitigation will not likely end up with a certain success after all. As a bunch of incompatibilities are to be addressed in php5, I suppose we don't always have to bother bringing light to such compromise. We need to progress somehow. Moriyoshi

« previous php.internals (#1679) next »