> > The problem I see with this approach is that a keyword for skipping > > parameters would really just be a stopgap solution until something > > like Named Parameters can be added. > > > > Is it really appropriate to add a feature that only serves a temporary > > purpose? > > That was an argument in 2015. Today is 2019. We still have no named > parameters. And we could have had this functionality for four years. But by > all means, let's wait another 5 years before we can discuss again that we > shouldn't implement functionality that we could have today because maybe in 5 > years we could have a better one which nobody is working on and nobody has > any idea how to accomplish. That sounds like a practical approach that served > us well so far.
The [named parameters](https://wiki.php.net/rfc/named_params) was proposed in 2013. Does the problems which stopped us before still exist in 2019? Since we all agree named parameter should be a better solution, why not take a look at it first? Best regards, CHU Zhaowei -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
