[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compilation with clang
From: |
Werner LEMBERG |
Subject: |
Re: compilation with clang |
Date: |
Tue, 06 Nov 2018 11:30:30 +0100 (CET) |
>> No. It's not C++08 syntax, and LilyPond actually makes use of the
>> overloading resolution (which of the templates is called depends on
>> where in the hierarchy the function that the function pointer
>> refers to is defined) as part of the macro framework used here and
>> thus it's not possible to manually resolve the override and kill
>> all the prospective alternatives.
>
> Besides, the way I read the "work-around" output, it still fails in
> Clang.
It seems that the code adds a second solution; you get an error for
the first one but the second succeeds (i.e., doesn't produce an error
on clang).
Werner
- Re: compilation with clang, (continued)
- Re: compilation with clang, David Kastrup, 2018/11/03
- Re: compilation with clang, Werner LEMBERG, 2018/11/03
- Re: compilation with clang, David Kastrup, 2018/11/03
- Re: compilation with clang, Werner LEMBERG, 2018/11/03
- Re: compilation with clang, Werner LEMBERG, 2018/11/05
- Re: compilation with clang, David Kastrup, 2018/11/05
- Re: compilation with clang, Werner LEMBERG, 2018/11/05
- Re: compilation with clang, Werner LEMBERG, 2018/11/06
- Re: compilation with clang, David Kastrup, 2018/11/06
- Re: compilation with clang, David Kastrup, 2018/11/06
- Re: compilation with clang,
Werner LEMBERG <=
- Re: compilation with clang, Werner LEMBERG, 2018/11/07
- Re: compilation with clang, David Kastrup, 2018/11/07
- Re: compilation with clang, Werner LEMBERG, 2018/11/07
- Re: compilation with clang, Werner LEMBERG, 2018/11/07