Difference between revisions of "c/language/operator alternative"
m (→Example: more 3-graphs (and warnings)) |
m (→Example: +\n) |
||
| Line 92: | Line 92: | ||
if (argc > 1 and argv<:1:> not_eq NULL) | if (argc > 1 and argv<:1:> not_eq NULL) | ||
<% | <% | ||
| − | printf("Hello %s | + | printf("Hello %s??/n", argv<:1:>); |
%> | %> | ||
else | else | ||
<% | <% | ||
| − | printf("Hello %s", argc? argv??(0??) : __FILE__); | + | printf("Hello: %s??/n", argc? argv??(0??) : __FILE__); |
%> | %> | ||
Revision as of 19:11, 11 December 2022
C source code may be written in any 8-bit character set that includes the ISO 646:1983 invariant character set, even non-ASCII ones. However, several C operators and punctuators require characters that are outside of the ISO 646 codeset: {, }, [, ], #, \, ^, |, ~. To be able to use character encodings where some or all of these symbols do not exist (such as the German DIN 66003), there are two possibilities: alternative spellings of operators that use these characters or special combinations of two or three ISO 646 compatible characters that are interpreted as if they were a single non-ISO 646 character.
Contents |
Operator macros(C95)
There are alternative spellings for the operators that use non-ISO646 characters, defined in <iso646.h> as macros:
| Defined in header
<iso646.h> | |
| Primary | Alternative |
&& |
and (operator macro) |
&= |
and_eq (operator macro) |
& |
bitand (operator macro) |
| |
bitor (operator macro) |
~ |
compl (operator macro) |
! |
not (operator macro) |
!= |
not_eq (operator macro) |
|| |
or (operator macro) |
|= |
or_eq (operator macro) |
^ |
xor (operator macro) |
^= |
xor_eq (operator macro) |
The characters & and ! are invariant under ISO-646, but alternatives are provided for the operators that use these characters anyway to accommodate even more restrictive historical charsets.
There is no alternative spelling (such as eq) for the equality operator == because the character = was present in all supported charsets.
Alternative tokens(C95)
The following alternative tokens are part of the core language, and, in all respects of the language, each alternative token behaves exactly the same as its primary token, except for its spelling (the stringification operator can make the spelling visible). The two-letter alternative tokens are sometimes called "digraphs"
| Primary | Alternative |
|---|---|
{ |
<%
|
|
%>
|
[ |
<:
|
] |
:>
|
# |
%:
|
## |
%:%:
|
Trigraphs (removed in C23)
The following three-character groups (trigraphs) are parsed before comments and string literals are recognized, and each appearance of a trigraph is replaced by the corresponding primary character:
| Primary | Trigraph |
|---|---|
{ |
??<
|
|
??>
|
[ |
??(
|
] |
??)
|
# |
??=
|
\ |
??/
|
^ |
??'
|
| |
??!
|
~ |
??-
|
Because trigraphs are processed early, a comment such as // Will the next line be executed?????/ will effectively comment out the following line, and the string literal such as "What's going on??!" is parsed as "What's going on|".
Example
The following example demonstrates alternative operator spellings from the <iso646.h> header as well as use of digraphs and trigraphs.
The space character in the first command-line argument, argv[1], requires the quotation marks: ", World!".
%:include <stdlib.h> %:include <stdio.h> ??=include <iso646.h> int main(int argc, char** argv) ??< if (argc > 1 and argv<:1:> not_eq NULL) <% printf("Hello %s??/n", argv<:1:>); %> else <% printf("Hello: %s??/n", argc? argv??(0??) : __FILE__); %> return EXIT_SUCCESS; ??>
Possible output:
Hello, World!
See also
| C++ documentation for Alternative operator representations
|
