On Apr 18, 2009, at 1:17 PM, Ralf S. Engelschall wrote:
On Sat, Apr 18, 2009, Jeff Johnson wrote:
What do you want? An exception callback from popt? A post-facto
getter?
Hmmm... both would be sufficient, of course. For just this single
purpose a callback could be less intrusive. But in general I like C
APIs
where each(!) function stores detailed error information in the
context
object and then just returns the numerical and less detailed return
code. The caller then can be happy just about the numerical return
code
or call a getter to retrieve the detailed error message. So, in the
long-term I would like to see the second one also in POPT...
Callbacks into an API/ABI have a speshul painfulness that I'd like
not to see in popt. Note that there's already means to do pre/post
per-table callbacks, an error callback will be overloaded into
the same mechanism if my feet are roasted with a burning poker.
Getter coming up soonestly, and popt-1.16 and other trickle
effects as rapidly as I can manage.
The whole point of pushing into popt was less code that
could be more generally used, not multiple implementations
rotting under #ifdef's. Not that OpenPKG code is rotten
by any means, but you know what I mean ...
todo++
73 de Jeff
Ralf S. Engelschall
r...@engelschall.com
www.engelschall.com
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
