Werner LEMBERG <w...@gnu.org> 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 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
