Hi!
My opinion is that solution tries to overcome bad consequences of
legacy code, when it's not feasible to change something without
breakage a lot of code, although the real solution is to refactor
functions with long variable lists (as Uncle Bob says), maybe this
should be noted in documentation of this feature.
Alan nicely highlighted all cons of this feature, but instead of
voting against it I suggest to put that into the docs, so people can
use it wisely and understand consequences.
One question about implementation:
Given we have this function
> function create_query($where, $order_by, $join_type='', $execute = false,
> $report_errors = true) {}
and this statement
> On the engine level, it will be implemented by putting NULL in the place
> where the parameter is passed.
what value $join_type will get on this call?
create_query("deleted=0", "name",,, /*report_errors*/ true);
NULL or empty string? I.e. will optional parameters always get NULLs
or their default values?
Thanks.
--
Regards,
Shein Alexey
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
