[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C++11 now default?
From: |
Mike Miller |
Subject: |
Re: C++11 now default? |
Date: |
Wed, 24 Feb 2016 10:46:13 -0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Wed, Feb 24, 2016 at 13:12:57 -0500, John W. Eaton wrote:
> I checked in a series of changes. Now the only warnings I see from Clang
> are about unused functions. Those seem pretty harmless, but I may look at
> eliminating them as well.
Do you not see the following with your version of clang?
../liboctave/util/sparse-util.cc:38:1: warning: all paths through this function
will call itself [-Winfinite-recursion]
{
^
1 warning generated.
Code is marked with a FIXME.
Other than that, I agree I only see warnings about unused functions now.
Thanks,
--
mike
- Re: C++11 now default?, (continued)
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?,
Mike Miller <=
- Re: C++11 now default?, John W. Eaton, 2016/02/24
- Re: C++11 now default?, John W. Eaton, 2016/02/25
- Re: C++11 now default?, Ben Abbott, 2016/02/24
- Re: C++11 now default?, Mike Miller, 2016/02/24
- Re: C++11 now default?, Ben Abbott, 2016/02/24
- Re: C++11 now default?, Mike Miller, 2016/02/23
Re: C++11 now default?, John W. Eaton, 2016/02/25
Re: C++11 now default?, Rik, 2016/02/23