Hi! > They are seen and promoted as core features. Whether we like that idea > or not is not really relevant. We messed that up by making most of the > "Standard" PHP Library an extension for only political and licensing > reasons.
I think you using "core" here in two difference meanings, and the question of political and licensing reasons is completely irrelevant to current discussion. The question is that we have language core (keywords, syntax constructs, etc.) and we have various APIs. Unfortunately, due to disagreement among PHP developers, there's no consistent policy among APIs on the question of how to handle errors. However, there is a consistent policy about how to do it when we're talking about core PHP constructs - keywords, language syntax, etc. - that we do not use exceptions there. > We can't really change existing code without breaking everything out > there. So we somehow have to do it on a case by case basis or for new > stuff only. We have to have clear policy that can be understood by users. Doing it on a whim of a person that submits particular patch was what we were doing before, and it didn't work very well for us. The consensus by this point was that PHP keywords, language constructs, etc. do not throw exceptions (the unfortunate patch of 2005 aside). If you want to change this - fine, please propose a consistent policy that changes it, let's agree on it and adopt it. But doing it in random places just because it seemed convenient at this moment IMO is not a good idea. It is IMO exactly what we are trying to fix. -- 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
