Hello,

On Wed, May 28, 2008 at 10:25 AM, Jani Taskinen <jani...@sci.fi> wrote:

It's not syntax sugar, it's a construct which is used across many other languages. It will improve the language for other people and might help people to learn PHP. If we have resource issues commiting one line of grammar the project has other issues to deal with.

Anyone who has gotten to a level of knowing how to assign php variables will likely have any troubles understanding what: $config = ['smtpHost' => 'example.org']; $oSmtp = someSmtpTransport($config['smtpHost']);

Is doing, and if you have a super complex multi-dimensional array, regardless of brackets or array syntax it will be hard to understand by a php new comer.

var_dump($foo); $foo = ['foo' => 'bar']; var_dump($foo);

Explained.

We already face issues with more then one way to do things, we deal with it and it has not proven to be to difficult.

compatible code just like you do with PHP4 classes and PHP5 classes.

their besides the people on this list who are accustomed to such use for arrays. Also, a community of developers who would like an alternative syntax to array to clean up their code a little, like me.

class Foo { public $bar; public $baz; public $qux;

VS

class Foo { public $bar, $baz, $qux;

$obj = new Stdclass; $obj = (object) NULL;

Really guys my only point is that we should not disregard a proposal for the sake of having more then one way to do something. That is the beauty of PHP and any successful language, it appeals to a wide variety of coding standards, methodologies and paradigms. If you just think about it you can name tons of things in PHP that let you do the same thing with two syntax's. This is part of php's success. Some things are easier for people to learn then they are for others.

-Chris