On Wed, Jun 8, 2011 at 11:22, Lars Magnusson <lav...
> I'm unsure why you would want this. Is it primarily to have "a record"
> of progress, or just to avoid the exceptions.
In the case of PartiallyImplemented, I will give one example. I've
seen some API's are called in a particular scenario, and they are "not
implemented" and therefore an exception is thrown. Yet, I've
discovered that in the current scenario I am investigating, no action
is required to achieve some level of functionality. So, I would like
to remove the exception in that case, but still mark that it as not
been fully implemented.
Regarding the NotStartedYet case, I think this should normally throw
an error with a debug build, but not throw one for a release build.
For a "release" build if we throw the error, then it gains no value
except perhaps introducing an exception when the code might actually
> I personally like the exception, because it immediately lets me know
> that this functionality has not been implemented yet. If this is the
> case I usually implement the needed functionality before continuing on
> what I was doing. It seems to me that to spend time to change all the
> NotImplementedExceptions to call some static class is a waste of time.
> This time would be better spent actually implementing the
I agree. I hope it would not be a significant diversion. I'm just
trying to find a way for the libraries to be less likely to hit an
exception in particular build type scenarios.