I read about error management and I try now to throw errors in my application when something is wrong.
At some point, my application checks the state of an object. It must follow some rules, and I want to know if the rules are broken. If I throw an Error as soon as I find something wrong, I won't get all the errors listed but just the first.
I want to be able to tell the user, "you have to correct this, and that, and that" (like FlashBuilder does when you have compilation errors), not just "correct this and check again, there may be another error".
In this case, do you think it's possible/preferable to throw Error ? Or just register errors and return false when I found at least one error ?
Throwing interrupts processing, so you should build up a list of problems.