Hi, You all have right. Such errors can be catched by well written tests.
But on the other side, if you try to access in: - php - unset variable - you've got notice - php - inexistent key in array - you've got notice - sql - inexistent column - you've got sql error - java - inexistent key in hashmap - you've got exception You don't have to write special tests to catch all those errors. I have bad experience with large project written in php, in which NOTICES are disabled in php error reporting. It isn't covered by tests and it's very annoying when you loose half an hour looking for error in algorithm which is due to stupid typo in array key name. For me it's kind of environment which hides errors. What i like in symfony is that it doesn't hide such stupid errors. Because of such things as: - for default it enables php notices - i've got exception when i pass wrong option to function or methos which takes array of options as argument As of getAttribute behavior - i think it just can hide errors. I don't say that it should have some special functionality to expose them. But it would be nice if it wouldn't hide them. I know that it's because of it's "default" functionality, but it would be nice if such functionality could be optional (just passing null as second parameter). That's the only one thing that i don't like in symfony. I know - i have to learn to live with it, but maybe i just hoped that i'm not alone with such opinion ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
