I came across a situation where I would like to step back through the app’s methods up the “tree” until I decided to catch it (if I do) – like an exception; it’s raised through all the code until you catch it or hits the roof.
The general concensus is that you only use exception for exceptions. That being the case, what would be the mechanism to apply an exception like pattern in code but not necessarily an exception?
Is an exception the right mechanism to use? In this case, an exception does what’s needed – but by strict definition it’s not an exception.
Is there an event pattern or class I’m not aware of?
Edit
Just to clarify – my initial design would be to create a custom exception – since exception fits the bill. But this isn’t an exception – it’s a decision to go back through the code until I catch it or not – depending. I’m thinking custom exception – but want to make sure there isn’t a class/patter that handles this.
Update
I ended throwing a custom exception. While I always thought this was the best pattern/method to what I wanted, I didn;t like the use of an exception for this – since it’s not an exception. But ultimately, an exception is the perfect solution.
You could derive your own inherited exception class and then throw that, this specific exception could then be handled in your own specific way.