[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compilation with clang
From: |
David Kastrup |
Subject: |
Re: compilation with clang |
Date: |
Sat, 03 Nov 2018 20:00:08 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Werner LEMBERG <address@hidden> writes:
>>> Looking around in the internet it seems that this is a real
>>> problem, violating the C++11 standard, cf.
>>>
>>>
>>> https://stackoverflow.com/questions/33872039/invalid-explicitly-specified-argument-in-clang-but-successful-compilation-in-gcc
>>>
>>> Unfortunately, I'm completely stuck with a fix – my C++ knowledge
>>> is simply too limited. Anyone here who could help?
>>
>> I thought that they had fixed this.
>
> Well, the comments in the above link say that the stackexchange
> example is buggy and that there isn't a bug in clang, cf.
>
> https://bugs.llvm.org/show_bug.cgi?id=25693
>
>> Rewriting this in a manner not relying on the C++11 (and earlier
>> IIRC) resolution rules is not all that feasible: this is really
>> heavily making use of it. You'd have to do the whole method finding
>> business in a completely different manner.
>
> Are you *sure* that lilypond's code conforms to C++11?
I had read the standard on this after the first report. It was pretty
clear I thought. We had a discussion then. I think that Mojca reported
it then, maybe you can look this up.
> Could you extract a MWE so that I can create a question on
> stackexchange?
What would that be good for?
--
David Kastrup
- 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/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, 2018/11/06
- Re: compilation with clang, Werner LEMBERG, 2018/11/07
- Re: compilation with clang, David Kastrup, 2018/11/07