[MOAB-dev] Discussion on return type of MOAB routines

Jed Brown jed at jedbrown.org
Wed Jan 22 13:21:21 CST 2014


"Tim Tautges (ANL)" <tautges at mcs.anl.gov> writes:
> This depends on how often it happens.  In all cases, IMO, a success condition should result in nothing more than a 
> POD-sized object (and I should add, no virtual table).  

vtables are just pointers like any other in terms of performance.

> If it's a non-success condition that is "expected" (normal condition
> that's handled by the calling code), IMO this shouldn't print anything
> by default.  If it's a non-success that's also unexpected, printing is
> fine (including stack trace).

I don't believe in expected failures.  I find keeping expected and error
conditions in-band leads to confusing control flow, but YMMV.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20140122/e10371d4/attachment.pgp>


More information about the moab-dev mailing list