[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] [PATCH] libltdl error reporting

From: Peter O'Gorman
Subject: Re: [RFC] [PATCH] libltdl error reporting
Date: Thu, 10 Jun 2010 09:15:58 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]