Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99834
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain shust.com from 209.85.218.47 cause and error)
MIME-Version: 1.0
Date: Tue, 11 Jul 2017 15:02:18 +0000
Message-ID: <CAOe2Xe4j9dOa63wkG2gJxosH1fymWDB9C-zcXwDWGcB=Zw9w9g@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="001a113d46bcf7f8b205540bfcf2"
Subject: array coalesce operator concept
From: mark@shust.com (Mark Shust)

--001a113d46bcf7f8b205540bfcf2
Content-Type: text/plain; charset="UTF-8"

Hello,

I wanted to garnish feedback on a RFC proposal. This is just a concept at
this point, and is inspired by the null coalesce operator.

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) {

  echo $bar;

}


will result in the error:

PHP Warning:  Invalid argument supplied for foreach() in test.php on line 3


To prevent this, the logical solution is to wrap this in an is_array check:

<?php

$foo = "abc";

if (is_array($foo)) {

  foreach ($foo as $bar) {

    echo $bar;

  }

}


This code runs successfully and does not error out. For a syntactic
sugar/improvement, this can be shorthand for executing the loop instead of
wrapping the block within an is_array check:


<?php

$foo = "abc";

foreach (??$foo as $bar) {

  echo $bar;

}


Let me know your thoughts.


Cheers,
Mark

--001a113d46bcf7f8b205540bfcf2--