posted 21 years ago
You have a requirement that you have to do something with a value that doesn't exist? Well, as I see it, you've got a few options: you could make a value up (for example, always return 0); you could define and document a value (0 for normal return, -1 for RuntimeException, -2 for error, for example); or, and I know this is a crazy idea, you could talk to the customer about the requirement!
If you, as a developer, get a meaningless requirement, the only professional course of action is to try to get the requirement clarified.