Hi! > It's a point of view, not something the language should enforce.
It is a point of view that any proper language should enforce. Languages always enforce certain style, certain ideas and certain paradigm - be it computer languages or natural languages. You can decide from now on in your language the word "gloobloobla" would mean "hello, how are you today?" but if you try to use it to communicate with other people they would think you're not well. Language is a set of conventions, and this proposal flies in the face of all conventions that are commonly used and accepted not only in PHP but in the wider world of OO and modern programming in general. We don't need to import Visual Basic mistakes decades after they were made and recognized as such. See e.g.: http://stackoverflow.com/q/11596045/214196 > You may have a lib/object/chunk of code which raises exceptions, because > its developer thought some error is not recoverable; but when you use > it, you don't want to break your program's execution. That's why you have try/catch. -- 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
