Hey if you want to push to the extreme the logic of the "computer scientist" you were talking about in my office, then return the previous callback and let the upper layer do the right thing. Suppose they don't screw up for once ...
On Jun 8, 2011, at 17:37 , Wesley Bland wrote:
> Again, you are correct. Rather than just returning the previous callback (if any) I think it makes more sense to maintain a list of callbacks and have the errmgr call them directly. That way applications/ompi layers don't have to worry about calling another callback function.