From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2690 invoked by alias); 18 Feb 2010 19:51:11 -0000 Received: (qmail 2680 invoked by uid 22791); 18 Feb 2010 19:51:10 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-bw0-f212.google.com (HELO mail-bw0-f212.google.com) (209.85.218.212) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Feb 2010 19:51:06 +0000 Received: by bwz4 with SMTP id 4so125063bwz.8 for ; Thu, 18 Feb 2010 11:51:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.36.207 with SMTP id u15mr4492764bkd.187.1266522664205; Thu, 18 Feb 2010 11:51:04 -0800 (PST) In-Reply-To: <4B7D90B5.4020707@cs.utexas.edu> References: <4a00655d1002171047t4e87fb85w88b609245e3f9a8e@mail.gmail.com> <4B7D90B5.4020707@cs.utexas.edu> From: Rhys Ulerich Date: Thu, 18 Feb 2010 19:51:00 -0000 Message-ID: <4a00655d1002181150j3975f69bk29084d5b50eeb974@mail.gmail.com> Subject: Re: Feedback from GSL folks on libflame 4.0 To: jungman@lanl.gov Cc: gsl-discuss mailing list , "Field G. Van Zee" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00027.txt.bz2 Hi Gerard, >> (4) According to the manual, libflame calls abort() when it encounters >> =A0 =A0a problem. As I have discussed before, this is brain-damaged. It >> =A0 =A0makes it hard for other library developers (us) to integrate >> =A0 =A0their 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 reg= ard? - Rhys