I've used to 'options as array' pattern in PHP plenty of times. While it's probably the closest thing to named parameters you can get in that language, it can get kind of ugly and clumsy when you have to validate it.
function something(array $options, $defaults=array('foo'=>1,'bar'=>2)){
...(array_intersect_key or something)...
}
Actual named parameters would work so much better.
And Wordpress 'solves' this in the plugins API by suggesting using extract(), which converts an array into variables. Which is even worse.
After six years of programming in Python I've almost forgot that there are languages that don't have named function parameters.
I remember the horror of working with WINAPI. There are WINAPI functions with 10 or so arguments and I was using Delphi which as far as I remember had no support for dictionary literals, let alone named parameters.
Back in highschool, I wrote an Uno clone for a final project in Java. I ended up encountering a similar issue for when I was defining constructors for Card objects. At some point, I had to cast null as an Object to rid of some ambiguity. Still pretty embarrassed about it.
The problem with this approach is that you basically lose all IDE support and static code checking - it's a good solution in extreme cases, but I prefer not to use it as the default.
And Wordpress 'solves' this in the plugins API by suggesting using extract(), which converts an array into variables. Which is even worse.