Hi! > This proposal is about code modularization. Software engineering is > a history of better modularization. > > - Structured programming > - Object Oriented programming > - AOP > - DbC > > Exception is one of them.
I'm sorry, I have hard time understanding what exceptions have to do with modularization. Modularization is in my book creating a stand-alone reusable software components that are responsible for distinct task or set of tasks and have a well-defined API for that. I don't see where exceptions fit here. > While error handling without exception works, it decreases modularization. I don't see how. In what aspects and by what modularization is decreased? > Besides modularization, consistency is important for programming > language also. Consistency is important, true. But I don't see why there's less consistency in producing null values. On the contrary, the situation where the same operation called via factory method can produce null result, but literally exactly the same code called in different way via "new" operator can not and would produce exception instead - doesn't seem very consistent to me. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
