[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 17:26:38 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Werner LEMBERG <address@hidden> writes:
> ./include/translator.hh:78:3: note:
> expanded from macro 'TRANSLATOR_FAMILY_DECLARATIONS'
> DECLARE_TRANSLATOR_CALLBACKS (NAME); \
> ^
> ./include/translator.hh:97:14: note:
> expanded from macro 'DECLARE_TRANSLATOR_CALLBACKS'
> static SCM method_finder () { \
> ^
> ======================================================================
>
> 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. 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.
--
David Kastrup
- compilation with clang, Werner LEMBERG, 2018/11/03
- Re: compilation with clang,
David Kastrup <=
- 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, 2018/11/06