Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99862
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.177 as permitted sender)
To: Mark Shust <mark@shust.com>, internals@lists.php.net
References: <CAOe2Xe4j9dOa63wkG2gJxosH1fymWDB9C-zcXwDWGcB=Zw9w9g@mail.gmail.com>
Message-ID: <e86afbf8-25a3-c228-f4c9-53b9bc773ff4@gmail.com>
Date: Wed, 12 Jul 2017 11:00:12 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAOe2Xe4j9dOa63wkG2gJxosH1fymWDB9C-zcXwDWGcB=Zw9w9g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] array coalesce operator concept
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Code will error if a non-array value is passed through a looping feature.
> For example, this code:
> 
> <?php
> 
> $foo = "abc";
> 
> foreach ($foo as $bar) {

Looks like $foo??[] would work here. If $foo is something like false or
null, that is. If it's not, this is probably a serious bug (why would
you iterate on something that is a number or a non-iterable object) and
should be either fixed or resolved explicitly, not hidden.

-- 
Stas Malyshev
smalyshev@gmail.com