Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77656
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <542512B4.3000200@sugarcrm.com>
References: <CA+9eiLupqdnRWh3C=Q7Wa31NcDN_DUOa+uEXyAX78jcTn0OGcg@mail.gmail.com>
	<CAPwsocGF967ugDsACe0FALGJXY7NsgOT1TFAQE2sd2qxsskFaw@mail.gmail.com>
	<CA+9eiLuqfxBp-zQcc8aMFLAY53jHMsMu_PNSN6epdy62a+93KA@mail.gmail.com>
	<CAF+90c9ZKzFVozJpu3m54QM4=J22qgoLJ82NKr87v9jN=F3vpA@mail.gmail.com>
	<CAF+90c-30p5X2g1D-0fda-1pvGzta+QM5ETSra=1GdS9b=Y_7A@mail.gmail.com>
	<CA+9eiLvtub7jzW1_-2CThkABEfZ01W7Uz6Fx3n7QU2SrsMtR-Q@mail.gmail.com>
	<54248E27.1040206@sugarcrm.com>
	<CAPwsocFtU0qVvFgNsiKkx78WzSM+OodANjqUtYm_94+0RBJvqQ@mail.gmail.com>
	<54250F32.4080807@sugarcrm.com>
	<CAPwsocEnw9XDaKo28KuUfkcERkJHqeYeJAiY0GW6+0r3nLtXVg@mail.gmail.com>
	<542512B4.3000200@sugarcrm.com>
Date: Fri, 26 Sep 2014 12:38:47 +0400
Message-ID: <CA+9eiLvM2OW_jHE4gnx6sMTRvLf5fBSW4-_fOYWWfStThC6zaw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Leigh <leight@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec52d59877a71e60503f3d86d
Subject: Re: [PHP-DEV] [VOTE] Fix list() behavior inconsistency
From: dmitry@zend.com (Dmitry Stogov)

--bcaec52d59877a71e60503f3d86d
Content-Type: text/plain; charset=UTF-8

It's an inconsistent undocumented behavior, that started to work not by
design, but because of implementation issues.

<?php
list($a, $b) = "ab";
var_dump($a,$b);
?>
NULL
NULL

By the way, I'm agree, keeping string support might be better for
compatibility.

Thanks. Dmitry.

On Fri, Sep 26, 2014 at 11:16 AM, Stas Malyshev <smalyshev@sugarcrm.com>
wrote:

> Hi!
>
> > * Strings are _not_ treated as arrays of bytes everywhere.
>
> This is true. However, sometimes they are. E.g., $string[0] is
> meaningful, while array_flip($string) is not.
>
> > * If we intend to give strings more array-like support after this RFC
>
> We don't intend to give strings anything - both $string[0] and list($a,
> $b) = $string works right now. See here: http://3v4l.org/7AZFZ
>
> So you are arguing for BC break for no reason at all.
>
> > (like foreach($string as $char), making array_* work with strings),
>
> Nobody proposed that in this RFC, and it makes zero sense to propose it
> in this RFC, as this RFC is about list(), not about making strings into
> arrays which would require humongous amount of work and was not
> requested by anybody.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec52d59877a71e60503f3d86d--