[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: __attribute__((__unused__)) problem
From: |
Akim Demaille |
Subject: |
Re: __attribute__((__unused__)) problem |
Date: |
Thu, 11 Apr 2013 12:40:54 +0200 |
Le 11 avr. 2013 à 09:23, John Horigan <address@hidden> a écrit :
> I was only suggesting it for the YYERROR handler, where runtime performance
> is not a concern. For the YYSTACK_RELOCATE macro there needs to be a
> #pragma to silence the C4127 warnings. I cannot comprehend why Microsoft
> would issue a warning for this incredibly common C idiom.
Agreed.
I'd like to avoid leaving too many #pragma everywhere, so if
someone has some experience on this regard, and good suggestions,
please speak up.
I think I'll stop here for 2.7.1, as it fixes real portability
bugs so should be released asap.
- Re: __attribute__((__unused__)) problem, (continued)
- Re: __attribute__((__unused__)) problem, Akim Demaille, 2013/04/08
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/08
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/08
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/08
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/08
- Re: __attribute__((__unused__)) problem, Akim Demaille, 2013/04/10
- Re: __attribute__((__unused__)) problem, John Horigan, 2013/04/10
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/10
- Re: __attribute__((__unused__)) problem, Frank Heckenbach, 2013/04/11
- Re: __attribute__((__unused__)) problem, John Horigan, 2013/04/11
- Re: __attribute__((__unused__)) problem,
Akim Demaille <=
- RE: __attribute__((__unused__)) problem, victor khomenko, 2013/04/12