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


I always find it helpful to spell out the rest of the rule:

C++ Alternatives (reserved):
and and_eq bitand bitor compl not
not_eq or or_eq xor xor_eq


C++ Keywords:
asm do if return typedef
auto double inline short typeid
bool dynamic_cast int signed typename
break else long sizeof union
case enum mutable static unsigned
catch explicit namespace static_cast using
char export new struct virtual
class extern operator switch void
const false private template volatile
const_cast float protected this wchar_t
continue for public throw while
default friend register true
delete goto reinterpret_cast try

corey

On Thu, 03 Mar 2005 08:03:09 -0600, Eljay Love-Jensen <eljay@adobe.com> wrote:
> Hi Kannan,
> 
>  >Could you please tell us the option for allowing them to use as variable
> names?? We tried to get that info. But could not get that info!!
> 
> From:
> http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/C_002b_002b-Dialect-Options.html
> 
> -fno-operator-names
> Do not treat the operator name keywords and, bitand, bitor, compl, not, or
> and xor as synonyms as keywords.
> 
> HTH,
> --Eljay
> 
>


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