Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42357 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63489 invoked from network); 19 Dec 2008 23:43:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Dec 2008 23:43:50 -0000 X-Host-Fingerprint: 89.76.8.74 chello089076008074.chello.pl Received: from [89.76.8.74] ([89.76.8.74:24096] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DA/DB-00764-4B13C494 for ; Fri, 19 Dec 2008 18:43:48 -0500 Message-ID: To: internals@lists.php.net Date: Sat, 20 Dec 2008 00:43:45 +0100 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 89.76.8.74 Subject: Undefined constants producing E_NOTICE From: faw217@gmail.com (Kuba Wieczorek) Hello everyone, Currently when an undefined constant is called, E_NOTICE is produced and the name of the constant is assumed to be a string. In my opinion this behaviour is strange and problematic for most developers. Maybe it would be good if invoking undefined constants will start to produce at least E_WARNING? For the moment some unexpected behaviour caused by use of undefined constant may be hard to fix with low error reporting level. Moreover, treating an undefined constant as a string does not make sense. I know that PHP is intended to be a flexible language, but for me it's a bit thick. Regards, faw