[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 'noreturn' warning in libcruft
From: |
John W. Eaton |
Subject: |
Re: 'noreturn' warning in libcruft |
Date: |
Wed, 8 Aug 2012 12:11:18 -0400 |
On 7-Aug-2012, Rik wrote:
| On 08/07/2012 02:28 PM, John W. Eaton wrote:
| > On 7-Aug-2012, Rik wrote:
| >
| > | This seems fine. It is a niggling little warning so I didn't want to
spend
| > | too much time constructing the generalizable solution.
| >
| > Do you want to work on this, or would you like for me to do it?
| Can you do this?
OK, I checked in the following changes:
http://hg.savannah.gnu.org/hgweb/octave/rev/87411930d6c4
http://hg.savannah.gnu.org/hgweb/octave/rev/4d52239daef5
I didn't use the gnulib stdnoreturn module because it wasn't clear to
me how best to do that *and* get the HAVE_ATTR_NORETURN macro that we
need without duplicating the logic of the module.
jwe
- Re: 'noreturn' warning in libcruft, (continued)
- Re: 'noreturn' warning in libcruft, Michael Goffioul, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Michael Goffioul, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Rik, 2012/08/07
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07
- Re: 'noreturn' warning in libcruft, Rik, 2012/08/07
- Re: 'noreturn' warning in libcruft,
John W. Eaton <=
- Re: 'noreturn' warning in libcruft, John W. Eaton, 2012/08/07