This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC compiler issue - parse error before `&&' token

From: corey taylor <corey dot taylor at gmail dot com>
To: Eljay Love-Jensen <eljay at adobe dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Thu, 3 Mar 2005 10:33:53 -0600
Subject: Re: GCC compiler issue - parse error before `&&' token
References: <5b7094580503030434e3ed62a@mail.gmail.com> <00fe01c51ff6$d753b3d0$2a0e000a@blr.velankani.com> <6.2.1.2.2.20050303080053.021e34b0@iplan-mn.corp.adobe.com> <2e393d0805030308194bd4f71@mail.gmail.com> <6.2.1.2.2.20050303102449.021e3da8@iplan-mn.corp.adobe.com>
Reply-to: corey taylor <corey dot taylor at gmail dot com>

Ah yes, I didn't mean to make that unclear.  They are under 2.11 for
the user interested.

I find it interesting they don't specify the word 'keyword' in that
second section. "Furthermore, the alternative representations shown in
Table 4 for certain operators and punctuators (2.5) are
reserved and shall not be used otherwise:"

corey

On Thu, 03 Mar 2005 10:28:42 -0600, Eljay Love-Jensen <eljay@adobe.com> wrote:
> Hi Corey,
> 
> Those C++ Alternatives (reserved) *are* C++ Keywords.
> 
> As per both ISO 14882 and Stroustrup's C++ Programming Language (special
> edition) Appendix A.
> 
> --Eljay
> 
>

References:
- Re: GCC compiler issue - parse error before `&&' token
  - From: Brian Budge
- RE: GCC compiler issue - parse error before `&&' token
  - From: Kannan
- RE: GCC compiler issue - parse error before `&&' token
  - From: Eljay Love-Jensen
- Re: GCC compiler issue - parse error before `&&' token
  - From: corey taylor
- Re: GCC compiler issue - parse error before `&&' token
  - From: Eljay Love-Jensen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]