Re: Try/Catch
- Posted by jimcbrown (admin) Feb 17, 2015
- 3863 views
Just make sure to wrap the "Get resource" part with a delete_routine() that calls the wrapper for the "Return resource" part.
So now I have to carefully go through the whole suite of libraries wrapping both get & release calls and replacing those in the code whereever they were called before.
And make sure all future modules follow the same bubble-wrapped pattern.
Only the get calls, and considering that it's the addition of a single statement (if even that) for each get call, I don't see what the big deal here is.
And sift through the allocators to make sure there is no inadvertent double reference.
Err, I don't see why this is necessary.
That's a lot of work to do just to protect my programs being bled by your exceptions.
There just has to be a better way.
Perhaps, but I should point out that SSC has the same problem. That is, whatever that better way is, it applies to SSC and try-catch equally, and without it both suffer equally.
