On Fri, Sep 26, 2014 at 11:54 AM, Xinchen Hui <larue...@php.net> wrote:
> Hey:
>
>
>
> On Fri, Sep 26, 2014 at 6:10 AM, Dmitry Stogov <dmi...@zend.com> wrote:
>> I told it doesn't support strings and objects because it was designed this
>> way.
>> I don't know who and when did it.
>>
>> It's not complicated to change it in any way.
>> The question which way is better, and it's the reason of voting.
>>
>> I would prefer not to extend list() to support strings, but in case
>> "enabling" would win, I'll make it.
>>
>> Thanks. Dmitry.
>>
>    I am working what should we do if none side get 2/3 votes?
worrying

>    it seems it is going there :<
>
> thanks
>>
>>
>>
>> On Fri, Sep 26, 2014 at 1:50 AM, Stas Malyshev <smalys...@sugarcrm.com>
>> wrote:
>>
>>> Hi!
>>>
>>> > It was on design. list() was intended to support plain arrays only.
>>>
>>> I'm not sure I'm getting this point - why list($a, $b) = $foo is not
>>> just translated as $a = $foo[0], $b = $foo[1], etc.? Is it hard to make
>>> it work that way?
>>>
>>> --
>>> Stanislav Malyshev, Software Architect
>>> SugarCRM: http://www.sugarcrm.com/
>>>
>
>
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/



-- 
Xinchen Hui
@Laruence
http://www.laruence.com/

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to