Hi Stanislav

I would not agree with your argument that it should be introduced because it
is requested by real people for years and it is simple to add. Isn't that
pretty much the same as "because we can"?
IMO we should wait with this RFC if Nikita is willing to write an RFC for
named parameters including an implementation afterwards, because I think
named parameters would address the problem way better. The skipping
parameters as in your proposal would then just be the ugly alternative.
However, if the RFC for named parameters will not be created or rejected,
then I would appreciate your RFC.

Best,
Robert

-----Ursprüngliche Nachricht-----
Von: Stas Malyshev [mailto:smalys...@sugarcrm.com] 
Gesendet: Montag, 2. September 2013 22:12
An: Nikita Popov
Cc: PHP Internals
Betreff: Re: [PHP-DEV] [RFC] Skipping parameters take 2

Hi!

> I think this doesn't really help readability. Right now you should 
> implement functions with many options with an $options array.

I don't understand. Who says I should do that? I certainly don't see how I
should.

> If we want to change something here, we should skip this step and go 
> right for named arguments. I think I'll give implementing them a try.

If you are ready to present named args proposal for 5.6, fine. But if not, I
think denying obviously requested feature (see links for requests in the
RFC) because some "pie in the sky" consideration is completely wrong.

I must say it seems a little strange for me given current stream of "because
we can" syntax additions proposed to reject something that has been asked
for by real people for years just because sometime in the future we might or
might not have something that may do a similar thing in different way.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

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



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

Reply via email to