My kneejerk reaction to this, as no one particularly important, is to
not allow mixing those syntaxes.
I looked at the RFC a minute ago, and I read a reference to a parallel
solution to this being named parameters. Which, I think, is not
accurate. The problem with the array() notation is definitely at deep
nesting levels. The fact that arrays as arguments suddenly look nicer is
basically just a bonus. I really just don't want to type array()
twenty-five times in the same data structure.
PS: That is not to say that I wouldn't love named parameters; I would
adore them. I can't count how many times I've thought that a router
would benefit enormously from being able to do that. However, using an
array instead worked fine - and that is cool.
- M.
On 6/1/2011 8:01 AM, Arvids Godjuks wrote:
My personal feel about this is that yes, short arrays are not bad, but
things like
$a = new A;
$a[array()];
just scare the crap of me when I see them. To me PHP is easy on syntax
and it's good. When I see Ruby or Python code with all it's crazy
magic I feel sick. Still one day I will have to learn one, but that
doesn't mean PHP should go that way too (i'm not alien to system
languages, I had some practice with Pascal, Delphi& C some years ago,
just wanted to go the WEB path so migrated to PHP).
If it's not too much, it would be good to avoid such strange
constructs at all, because people are mean and they tend to do bad
things in code.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
