Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41556
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain dmi.me.uk designates 213.171.205.116 as permitted sender)
Message-ID: <4908778F.8020705@dmi.me.uk>
Date: Wed, 29 Oct 2008 14:47:43 +0000
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: Josh <josh.sickmate@gmail.com>
CC: =?ISO-8859-1?Q?Pawe=3F_Stradomski?= <pstradomski@gmail.com>, 
 internals@lists.php.net, Arvids Godjuks <arvids.godjuks@gmail.com>
References: <6fef9b880810282117v569d3064l752902daaa285a25@mail.gmail.com>	 <9b3df6a50810282353oaedfde5qf62df50876760170@mail.gmail.com>	 <200810291001.47422.pstradomski@gmail.com>	 <49083290.2040104@dmi.me.uk> <6fef9b880810290345p4ddfe6bof62aeb217fd2aab2@mail.gmail.com>
In-Reply-To: <6fef9b880810290345p4ddfe6bof62aeb217fd2aab2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Constants in double-quoted strings
From: dave@dmi.me.uk (Dave Ingram)

Josh wrote:
> Dave, how is a variable name any less a bareword than a constant name?
>   
A bareword (in my opinion) is a word without a sigil (e.g. a leading $),
so the way that you would write a constant normally in PHP. What I was
trying to say is that having bareword-style interpolation ("{MYCONST}")
is much more likely to break BC than the "{#MYCONST}" style.

> Thats what the backets were for, perhaps combined with a symbol to
> make it even less likely, and of course if the constant is not found
> in the symbol table, the constant name would be outputted directly.
>   
But would it raise a warning, as PHP currently does for unrecognised
constants? If not, it could be argued that this would make subtle typos
harder to spot.


Dave