Hi! > We've had a problem recently where one of our developers forgot an "if".
We clearly have two contradicting directions here. On one hand, we have people that say giving '1' to a method expecting integer should be an error, and anything unexpected should generate warnings and errors because the code should handle exceptional cases explicitly. On the other hand, we have people who say "no matter what happens, just plow through and substitute nulls if something is wrong". Both approaches I guess have their advocates and their fans, and have good pro and contra arguments. What however I think can not be done is randomly taking both of these approaches in one language at a whim and expect it to make sense. PHP has taken enough criticism on this front and we don't need to add more to it. Either we say "if the call can't be done it's an error" or we say "if we can't call something we just return null" but not both. PHP currently treats methods that can't be called as an error. I think replacing it with "just return null" would not be a thing most PHP developers would want. -- 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
