I actually like the concept from .Net of a NotImplementedException
. You can easily define your own, deriving from std::exception
, overriding what
as "not implemented".
It has the advantages of:
- easily searchable.
- allows current & dependent code to compile
- can execute up to the point the code is needed, at which point, you fail (and you immediately have an execution path that demonstrates the need).
- when it fails, it fails to a know state, so long as you're not blanketly swallowing exceptions, rather than relying upon indeterminable state.