Jot,
> Le 20 nov. 2021 à 15:57, Jot Dot a écrit :
>
> Hi Akim,
>
>> Could you please attach that parser.h file? Or a link to it? Or at least
>> the
>> relevant excerpts, so that we can have a look at what confuses it.
>>
>> Did you make sure it compiled in C++11? Actually I would even make
>53 #if defined __cplusplus
>54 # define YY_CPLUSPLUS __cplusplus
>55 #else
>56 # define YY_CPLUSPLUS 199711L
>57 #endif
>
> Please check why your compiler does not define __cplusplus. Compliant
> compilers
> must define it properly so that we can know what version of C++17 w
> On 21 Nov 2021, at 13:02, Jot Dot wrote:
>
>> 53 #if defined __cplusplus
>> 54 # define YY_CPLUSPLUS __cplusplus
>> 55 #else
>> 56 # define YY_CPLUSPLUS 199711L
>> 57 #endif
>>
>> Please check why your compiler does not define __cplusplus. Compliant
>> compilers
>> must define it
Jot,
> Le 21 nov. 2021 à 13:02, Jot Dot a écrit :
>
>> 53 #if defined __cplusplus
>> 54 # define YY_CPLUSPLUS __cplusplus
>> 55 #else
>> 56 # define YY_CPLUSPLUS 199711L
>> 57 #endif
>>
>> Please check why your compiler does not define __cplusplus. Compliant
>> compilers
>> must def
>> "You need to compile with the /Zc:__cplusplus switch to see the updated value
>> of the __cplusplus macro. We tried updating the macro by default and
>> discovered
>> that a lot of code doesn’t compile correctly when we change the value of
>> __cplusplus"
> No worries. Should I understand tha
> Le 21 nov. 2021 à 15:21, Jot Dot a écrit :
>
>>> "You need to compile with the /Zc:__cplusplus switch to see the updated
>>> value
>>> of the __cplusplus macro. We tried updating the macro by default and
>>> discovered
>>> that a lot of code doesn’t compile correctly when we change the val
> Don't use semantic_type or YYSTYPE, just value_type.
>
> The name semantic_value is deprecated: it is supported by old parsers, but new
> ones use only value_type.
Ok. I replaced YYSTYPE with my parser's value_type.
I did a similar action for YYLTYPE (since that too is undefined).
Everything s
> Le 21 nov. 2021 à 20:01, Jot Dot a écrit :
>
> 1>D:\data\c\gen\Gen Parser\parser.cpp(987,42): warning C4003: not enough
> arguments for function-like macro invocation 'max'
> 1>D:\data\c\gen\Gen Parser\parser.cpp(987,42): error C2589: '(': illegal
> token on right side of '::'
>
> And the
> That's the usual BS of windows.h.
Sorry for putting you thru the nightmare I deal with on a regular basis :(
> https://stackoverflow.com/questions/11544073/how-do-i-deal-with-the-max-macro-in-windows-h-colliding-with-max-in-std
That worked. I placed #define NOMINMAX as the first line in my %co
Jot,
> Le 22 nov. 2021 à 01:42, Jot Dot a écrit :
>
> For %merge, what is the status where we discussed the possibility of putting
> the merge routine(s) as member functions of the generated parser class? That
> would indeed simplify my code for merges.
I had forgotten about that. Thanks for
10 matches
Mail list logo
