Feedback from GSL folks on libflame 4.0
Thu Feb 18 19:51:00 GMT 2010
>> (4) According to the manual, libflame calls abort() when it encounters
>> a problem. As I have discussed before, this is brain-damaged. It
>> makes it hard for other library developers (us) to integrate
>> their thing into an existing error-handling system.
> Bottom line: we are anything but married to the idea of aborting when an error
> is encountered, but we are unsure how to come up with a solution that is less
> brain-damaged and portable and that fits our users' coding style.
I'm willing to take a stab at providing the necessary error handling
underneath flame to make it play nice with GSL's error handling model.
The obvious choice is to adopt GSL's routines. However, flame is
LGPL and so adopting GSL's GPLed error handling directly is not an
Do you know of an LGPL project that you believe does a good job in this regard?
More information about the Gsl-discuss