Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • If you're looking for two separate answers, you should ask two separate questions. Combining them just makes it that much harder to answer. Commented Aug 5, 2013 at 13:18
  • 2
    @Bobson: I see these two questions as complementary: The former question is supposed to define the general context of the issue in broad terms, while the latter asks for specific information that should allow readers to draw their own conclusion. An answer doesn't have to give separate, explicit answers to both questions; answers "in-between" are just as welcome. Commented Aug 5, 2013 at 13:51
  • 5
    I'm unclear on something: What is the reason for deriving ValidationError from Exception, if you're not going to throw it? Commented Aug 5, 2013 at 14:06
  • @pdr: Do you mean in the case of throwing AggregateException instead? Good point. Commented Aug 5, 2013 at 15:27
  • 3
    Not really. I mean that if you're going to throw it, use an exception. If you're going to return it, use an error object. If you have expected exceptions that are really errors by nature, catch them and put them into your error object. Whether or not either one allows for multiple errors is entirely irrelevant. Commented Aug 5, 2013 at 17:34