Aside: I'm leaning away from upholding the
'drop-in-with-minimum-edits' philosophy for my rewrite, since the
dlfcn.h API seems like a pretty bad design to me. After all, all
people really need to do is call functions with a known name and
known signature which happen to be in another library. I'm seriously
contemplating using a *much* smaller and cleaner API, which ends up
with client code more along the lines of:
With that as a starting point, it's easy enough to maintain an error
stack in an exception struct that wraps around setjmp/longjmp, and to
plus some glue to make catching an error thrown from libltdl2 and for
unwinding the error stack inside it as easy as possible. WDYT?
I think it would be better in c++. I am unsure that a rewrite is
necessary though.
Peter
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
