--- Additional Comments From joseph at codesourcery dot com 2004-12-17
01:29 ---
Subject: Re: #elif token1 token2 doesn't produce a
diagnostic
On Thu, 16 Dec 2004, dpatel at apple dot com wrote:
> On Dec 16, 2004, at 1:01 PM, bangerth at dealii dot org wrote:
>
> > That's because it
--- Additional Comments From dpatel at apple dot com 2004-12-17 01:04
---
Subject: Re: #elif token1 token2 doesn't produce a diagnostic
Never mind, someone led me to believe that this is a Plum Hall test
failure. It is not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19040
--- Additional Comments From dpatel at apple dot com 2004-12-16 22:54
---
Subject: Re: #elif token1 token2 doesn't produce a diagnostic
Neil,
Would it be possible to quote standard here? We encountered this while
running Plum Hall tests, so I just wanted to make sure. Thank you.
-
--- Additional Comments From neil at gcc dot gnu dot org 2004-12-16 22:38
---
Not a bug - the standard requires this.
--
What|Removed |Added
Status|NEW
--- Additional Comments From bangerth at dealii dot org 2004-12-16 21:01
---
That's because it doesn't have to evaluate the #elif condition any more,
since it has already taken the #ifdef branch. If you change the code to
#ifdef BAR
return 1;
#elif BAR FOO
return
--- Additional Comments From dpatel at apple dot com 2004-12-16 21:07
---
Subject: Re: #elif token1 token2 doesn't produce a diagnostic
On Dec 16, 2004, at 1:01 PM, bangerth at dealii dot org wrote:
> That's because it doesn't have to evaluate the #elif condition any
> more,
> since
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-16
18:23 ---
Confirmed.
--
What|Removed |Added
Status|UNCONFIRMED |NEW
E
