From: Rhys Ulerich <rhys.ulerich@gmail.com>
To: jungman@lanl.gov
Cc: gsl-discuss mailing list <gsl-discuss@sourceware.org>,
"Field G. Van Zee" <field@cs.utexas.edu>
Subject: Re: Feedback from GSL folks on libflame 4.0
Date: Thu, 18 Feb 2010 19:51:00 -0000 [thread overview]
Message-ID: <4a00655d1002181150j3975f69bk29084d5b50eeb974@mail.gmail.com> (raw)
In-Reply-To: <4B7D90B5.4020707@cs.utexas.edu>
Hi Gerard,
>> (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
option.
Do you know of an LGPL project that you believe does a good job in this regard?
- Rhys
next prev parent reply other threads:[~2010-02-18 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a00655d1002171047t4e87fb85w88b609245e3f9a8e@mail.gmail.com>
2010-02-19 8:48 ` Field G. Van Zee
2010-02-18 19:51 ` Rhys Ulerich [this message]
2010-02-19 0:20 ` Gerard Jungman
2010-02-19 20:22 ` Brian Gough
2010-02-19 0:00 ` Gerard Jungman
2010-02-20 4:30 ` Field G. Van Zee
2010-02-23 13:13 ` Brian Gough
2010-02-24 1:42 ` Gerard Jungman
2010-02-19 18:19 ` Brian Gough
2010-02-19 18:41 ` Robert G. Brown
2010-02-19 20:57 ` Gerard Jungman
2010-02-19 21:46 ` Robert G. Brown
2010-02-19 22:34 ` Gerard Jungman
2010-02-22 23:09 ` Brian Gough
2010-02-23 10:50 ` Theodore Papadopoulo
2010-02-23 14:55 ` Robert G. Brown
2010-02-24 1:50 ` Gerard Jungman
2010-02-24 11:31 ` Robert G. Brown
2010-02-23 17:39 ` James Amundson
2010-02-19 20:07 ` Brian Gough
2010-02-19 20:54 ` Gerard Jungman
2010-02-20 4:31 ` Field G. Van Zee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a00655d1002181150j3975f69bk29084d5b50eeb974@mail.gmail.com \
--to=rhys.ulerich@gmail.com \
--cc=field@cs.utexas.edu \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@lanl.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).