Oh, and I almost forgot to mention: > If our intention is to really never use NotImplemented (except for > whenever we're internally developing new features) that might be > fine.
I'm thinking that NotImplemented throws will become a permanent part of some library components: if someone tries to construct a p=0 LAGRANGE or p=1 CLOUGH element, for example, that's not really a logic error on our part, that's the user asking for something that we can't implement. Those are just my half-formed thoughts on it, though. > But if we ship a release (like we just did) which has NotImplemented > stuff being thrown.... then we're not giving either our users or > ourselves very much info when someone runs into these cases. This is absolutely right. But I hope file/line number/tracefile is enough for now? --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
