Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43754 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2583 invoked from network); 21 Apr 2009 23:37:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Apr 2009 23:37:39 -0000 Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.133 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 83.243.58.133 mailout1.netbeat.de Linux 2.6 Received: from [83.243.58.133] ([83.243.58.133:46055] helo=mailout1.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 39/E6-10878-2C85EE94 for ; Tue, 21 Apr 2009 19:37:39 -0400 Received: (qmail 20391 invoked by uid 89); 21 Apr 2009 23:55:39 -0000 Received: from unknown (HELO ?192.168.1.102?) (johannes%schlueters.de@88.217.48.59) by mailout1.netbeat.de with ESMTPA; 21 Apr 2009 23:55:39 -0000 To: Kalle Sommer Nielsen Cc: Internals In-Reply-To: <2dedb8a0902061106p4333682g56a1ec29196e7f3e@mail.gmail.com> References: <2dedb8a0902061106p4333682g56a1ec29196e7f3e@mail.gmail.com> Content-Type: text/plain Date: Wed, 22 Apr 2009 01:37:35 +0200 Message-ID: <1240357055.6159.9.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Throwing E_DEPRECATED on startup From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Fri, 2009-02-06 at 20:06 +0100, Kalle Sommer Nielsen wrote: > I'd like to propose a change for when PHP starts to throw an > E_DEPRECATED notice for each of the deprecated ini directives (such as > register_globals, safe_mode ect.) like in HEAD where they just throw a > warning (more about that below). I have attached a patch for this in > 5.3 (which is the only branch this patch really relates to). Yeah. Good thing to notice the user of bad configuration. I'm wondering a bit how we can educate people about magic_quotes_gpc ... people who blindly disable them probably break stuff which is "secure" by accident. This is not only relevant to this patch though. The best idea I have is a clear pointer to the docs from the message ... johannes