Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42361
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 74.125.46.30 cause and error)
Message-ID: <494D1FFF.3090703@chiaraquartet.net>
Date: Sat, 20 Dec 2008 10:40:31 -0600
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807)
MIME-Version: 1.0
To: =?UTF-8?B?Q3Jpc3RpYW4gUm9kcsOtZ3Vleg==?= <crrodriguez@suse.de>
CC:  internals@lists.php.net
References: <DA.DB.00764.4B13C494@pb1.pair.com> <494CF47A.3000300@suse.de>
In-Reply-To: <494CF47A.3000300@suse.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Undefined constants producing E_NOTICE
From: greg@chiaraquartet.net (Greg Beaver)

Cristian Rodríguez wrote:
> Kuba Wieczorek escribió:
>> 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?
> 
> Use class constants
> 
> class foo {
> }
> 
> echo foo::BAR;
> 
> Fatal error: Undefined class constant 'BAR' ...
> 
> that's what you are really looking for... ;)

namespaced constants also cause fatal error when used with qualified name.

Greg