Hello Mike,
that is a good idea imo. Putting all the stuff in an extension that is per
default enabled in 6.0 and then in 6.1 moved to pecl. If everything
generates E_STRICT/E_NOTICE then we should be fine.
best regards
marcus
Tuesday, March 7, 2006, 5:51:42 PM, you wrote:
> Just a silly little brainstorm....
> What about moving those functions to a separate php extension where they
> can eventually be phased out? At least at that point you can get it all
> out of the core but still provide an easy way for people who need the BC
> to have it. (is there already a deprec extension somewhere?)
> On Tue, 2006-03-07 at 16:08 +0200, Zeev Suraski wrote:
>> At 12:27 07/03/2006, Pierre wrote:
>> >On 3/7/06, Derick Rethans <[email protected]> wrote:
>> > > On Tue, 7 Mar 2006, Stefan Esser wrote:
>> > >
>> > > >
>> > > > > That was the plan. Checking for register_globals should return
>> > > > > false.
>> > > >
>> > > > Pierre's list says it removes things like
>> > > > get_magic_quotes_gpc() ..., which is a NONO.
>> > >
>> > > yeah, agreed. And we should also throw errors when people make the
>> > > setting, as per
>> > > http://www.php.net/~derick/meeting-notes.html#register-globals
>> >
>> >What is the point of detecting something that does not exist anymore?
>>
>> The point is that breakage is aggregated, not binary. The more stuff
>> we break, the more difficult it is to port, and frankly, it's quite
>> likely that a non OO app could migrate fairly cleanly even to PHP 6
>> with unicode disabled (perhaps with minor
>> fixes). get_magic_quotes_gpc() is designed for apps to do something
>> differently depending on the value of magic_quotes_gpc. It's fine
>> that it's always off in PHP 6, but there's no reason not to keep this
>> function (to always return false) so that you don't have to fix God
>> knows how many lines of code to remove it.
>>
>> Zeev
>>
Best regards,
Marcus