Hi! > a) it kind of encourages using long lists of arguments (which is not > normally regarded as good practice)
This ship has sailed long ago, these lists are the reality. And rewriting all the code to change all function calls is in most cases completely infeasible. > c) the current situation would syntax error out on ,, as a function call > argument, which is handy if you accidentally typed ,, twice by accident. > if this changes, not only would you loose this syntax error, but it > would do unpredictable things. There are many situations where you could type something by accident and have it change the meaning of the call. For example, if to type: if($foo); bar(); then bar() would execute always. This does not prevent us from using ; as statement separator or from using if's. -- 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
