Re: Finalizers are dangerous
Bill Torpey
Hi Frank:
toggle quoted messageShow quoted text
Obviously I would prefer to remain as close as possible to upstream code, so forking is a last resort. That being said, you’ve been so far quite unreceptive to my concerns about crashing as a result of unloading the payload (and transport, for that matter) library code. The approach of checking if the payload library exists is a bit of a hack, and is not possible currently, since the mamaInternal_findPayload function is not exposed as part of the API. Are you planning to expose those functions? A better solution I believe would be separating out the unloading of the library code from the other activities needed to do a clean shutdown. I’ve created a fugly hack for that in the forked OpenMAMA code (see attached), but would much prefer something a bit more “elegant”, which would likely require changing the API, and I don’t want to do that without agreement from you. But so far you haven’t even agreed that this is a problem. I’m open to ideas, but I think we can do better than what you suggest. Regards, Bill
|
|