Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35539
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Sat, 16 Feb 2008 11:00:24 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1717639104.20080216110024@marcus-boerger.de>
To: Lars Strojny <lars@strojny.net>
CC: PHP Internals <internals@lists.php.net>
In-Reply-To: <1203124494.21896.7.camel@localhost>
References: <1203124494.21896.7.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] E_DEPRECATED for 5.3
From: helly@php.net (Marcus Boerger)

Hello Lars,

  thanks for doing the work. I'll apply the patch during next week. And yes
you should emit deprecation messages for use of INI settings that are going
to be dropped in 6.0.

marcus

Saturday, February 16, 2008, 2:14:54 AM, you wrote:

> Hi all,

> I've heard that E_DEPRECATED is still missing nevertheless its
> introduction is planned for 5.3. So I've wrote it [1] based on a
> slightly outdated patch by Felipe. The patch is so far complete, as far
> as I can tell, but one thing I'm wondering about is whether we should
> trigger E_DEPRECATED warnings if the related ini-settings are present
> (magic_quotes_gpc, magic_quotes_runtime, register_globals). I would say
> yes, but I need some advice where to do that.

> For the docs team: I've added links in the E_DEPRECATED messages to
> http://php.net/{migrate}#<deprecated func>. The "{migrate}"-part can
> later be easily replaced once the appendix to the migration guide which
> explains how to deal with this deprecations is set up.

> [1] http://lars.schokokeks.org/php/e_deprecated-2.diff

> cu, Lars



Best regards,
 Marcus