On 10/13/14 06:22, Jørgen Kvalsvik wrote:
The question came up here: https://github.com/qilicun/opm-core/pull/2
What does the project prefer to handle error codes from 3rd party libraries?
In this case, CHKERRXX is delegating to a print-error function and a
(C++) exception. Obviously, I prefer not to introduce a variable for
this and rather wrap the call in the macro (almost like a try-catch),
but I would of course conform to project style on this.
Well, I like a plurality of error tracking. Certainly, the latest,
slickest codes that may work great for one module but not another
is acceptable, especially when it is a very robust solution, imho.
That way each development team and push the envelop on error tracking.
Maybe a singular mechanism will emerge and maybe it will not; time will
tell. Cross that bridge when the softwares begin to stabilize.
However, nothing replaces standard out to an error log file; so each and
every module should mimimally support SIO to the traditional error log
file, imho. If some developers want to have a second, very slick
mechanism, then that is fantastic for the rest of us to admire and use
and discover any caveats.
Particularly in the heavy development phases, standard error log files
have existed for a very long time, for very excellent reasons, imho.
ymmv.
hth,
James
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
