Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

When were the 'and' and 'or' alternative tokens introduced in C++?

I've just read this nice piece from Reddit.

They mention and and or being "Alternative Tokens" to && and ||

I was really unaware of these until now. Of course, everybody knows about the di-graphs and tri-graphs, but and and or? Since when? Is this a recent addition to the standard?

I've just checked it with Visual C++ 2008 and it doesn't seem to recognize these as anything other than a syntax error. What's going on?

like image 530
shoosh Avatar asked Feb 17 '09 04:02

shoosh


People also ask

When was and operator added in C++?

They've been there since C++ 98.

What are the 6 tokens in C?

C Tokens are of 6 types, and they are classified as: Identifiers, Keywords, Constants, Operators, Special Characters and Strings.

How many tokens are there in C?

There are 6 types of C tokens : identifiers, keywords, constants, operators, string literals and other separators.


1 Answers

From the first ISO C++ standard C++98, this is described in 2.5/ Alternative tokens [lex.digraph]:


  1. Alternative token representations are provided for some operators and punctuators.
  2. In all respects of the language, each alternative token behaves the same, respectively, as its primary token, except for its spelling. The set of alternative tokens is defined in Table 2.
Table 2 - Alternative tokens      alternative primary | alternative primary | alternative primary     --------------------+---------------------+--------------------        <%          {    |    and         &&   |    and_eq      &=        %>          }    |    bitor       |    |    or_eq       |=        <:          [    |    or          ||   |    xor_eq      ^=        :>          ]    |    xor         ^    |    not         !        %:          #    |    compl       ~    |    not_eq      !=        %:%:        ##   |    bitand      &    | 

So it's been around since the earliest days of the C++ standardisation process. The reason so few people are aware of it is likely because the main use case was for people operating in environments where the full character set wasn't necessarily available. For example (and this is stretching my memory), the baseline EBCDIC character set on the IBM mainframes did not have the square bracket characters [ and ].

like image 117
paxdiablo Avatar answered Sep 19 '22 12:09

paxdiablo