I used before a private NotYetImplementedException. I'm refactoring my code to use the lang.NotImplementedException. One of my previous use cases is no longer possible :
try { ... } catch (... e) { throw new NotImplentedException("... <case description> ...", e); }
Does this usage seem useful for most of people ?
While I can't say that I would use it in the same way, I can see your point here -- the
exception is thrown to indicate a portion of code that hasn't been written yet. I find myself
stubbing things out in a similar way very frequently.
Any [lang] folks have a problem with this being added?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
