Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92294
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.215.44 cause and error)
MIME-Version: 1.0
Sender: me@daveyshafik.com
In-Reply-To: <CAESVnVoFQUe7g4DGkszG2gR3gT3EhwEe=+CaUksUcRp0metR2A@mail.gmail.com>
References: <CAESVnVoFQUe7g4DGkszG2gR3gT3EhwEe=+CaUksUcRp0metR2A@mail.gmail.com>
Date: Thu, 14 Apr 2016 03:37:06 -0700
Message-ID: <CANaX5nfHZGKwqO=1fvYBoEJjqceLX99FsWheQzH3=cbE5-UW5w@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c24064cbbaa405306f7949
Subject: Re: [PHP-DEV] Interpolation using ${} syntax with spaces inside the braces
From: davey@php.net (Davey Shafik)

--001a11c24064cbbaa405306f7949
Content-Type: text/plain; charset=UTF-8

Whitespace inside of { } should not matter, the contents should be
evaluated as an expression and it's results used to determine the variable
name, so ${great} should also be $my as in the other cases.

Is this related to the use of quotes around string array keys inside
strings?

e.g. "$foo[great]" does not evaluate to $foo['my'] but to $foo['great'].

- Davey

On Tue, Apr 12, 2016 at 8:08 PM, Sara Golemon <pollita@php.net> wrote:

> I'm trying to decide just whether or not
> https://bugs.php.net/bug.php?id=71927 is "working as intended" as well
> as what the expected behavior in this situation /should/ be.
>
> https://3v4l.org/HfU1g indicates that at the very least HHVM and PHP
> disagree on the correct output, and testing the same sort of
> expression in bash says that it's not having any of it; "invalid
> substitution" warnings abound.
>
> The PHP behavior is just kinda weird.  "${ great}" does constant
> interpolation yielding "$my" which in turn becomes variable
> interpolation and we find up with "my value".  I'm actually doubtful
> that PHP pulls off this juggling *by accident*, which is why I'm
> posting about it before even going to the extent of proposing an RFC.
>
> Does anyone have historical context on this and can explain the
> current behavior as "working as intended"?
>
> -Sara
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a11c24064cbbaa405306f7949--