Hi Dimitris,
On Feb 12, 2010, at 3:04 AM, Dimitris Servis wrote:
> Hi all
>
> I am trying to disable error printing in a multithreaded version of HDF5.
> Setting H5Eset_auto to NULL will only disable error printing for the current
> error stack and not completely, which means that calling this function once
> and handle errors at will does not work like in the single threaded version.
> Unless error printing is globally disabled, this means that functions built
> on top of the multithreaded HDF5 need a function call to disable it in every
> function. I'd rather avoid that, therefore I am asking if there's another way
> to do that.
Hmm, there's no current way to do that. I wonder if we should amend
the API calls that interact with the error reporting function to take another
parameter to indicate whether the error reporting function change is local
(per-thread) or global (for all threads). What do people think?
Quincey
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
