Hey, I've just spotted a problem with usage of Exception(s) class, this apples to most of framework, but especially to Form component.
Now we have `FormException` witch extends standard `Exception` class, and all others exceptions that extends `FormException`. I tend to make use of logic that was delivered and well designed in standard SPL exception hierarchy class (especially difference between `LogicException` and `RuntimeException` and their hierarchy), e.g. I log runtime exceptions, but directly mail alert about logic ones, this assertion becomes useless when we dont use hierarchy. My question is, should we consider correct use of standard SPL exception hierarchy, as a coding-standard? And one thing more, we should in my opinion decide to use one strategy for exceptions, SPL or not, now some parts of framework, uses SPL exceptions and some not, I thing this should be clarified, cheers, canni -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
