|
1 | 1 | pure2-cpp1-multitoken-fundamental-types-error.cpp2...
|
2 |
| -pure2-cpp1-multitoken-fundamental-types-error.cpp2(3,8): error: 'signed short int' - did you mean 'short'? |
| 2 | +pure2-cpp1-multitoken-fundamental-types-error.cpp2(3,8): error: 'signed short int' - did you mean cpp2::'short'? |
3 | 3 | pure2-cpp1-multitoken-fundamental-types-error.cpp2(3,8): error: 'signed short int' is an old-style C/C++ multi-word keyword type
|
4 | 4 | - most such types should be used only for interoperability with older code
|
5 | 5 | - using those when you need them is fine, but name them with these short names instead:
|
6 | 6 | short, ushort, int, uint, long, ulong, longlong, ulonglong, longdouble, __schar, __uchar
|
7 | 7 | - see also cpp2util.h > "Convenience names for integer types"
|
8 |
| -pure2-cpp1-multitoken-fundamental-types-error.cpp2(4,8): error: 'short int signed' - did you mean 'short'? |
| 8 | +pure2-cpp1-multitoken-fundamental-types-error.cpp2(4,8): error: 'short int signed' - did you mean cpp2::'short'? |
9 | 9 | pure2-cpp1-multitoken-fundamental-types-error.cpp2(4,8): error: 'short int signed' is an old-style C/C++ multi-word keyword type
|
10 | 10 | - most such types should be used only for interoperability with older code
|
11 | 11 | - using those when you need them is fine, but name them with these short names instead:
|
12 | 12 | short, ushort, int, uint, long, ulong, longlong, ulonglong, longdouble, __schar, __uchar
|
13 | 13 | - see also cpp2util.h > "Convenience names for integer types"
|
14 |
| -pure2-cpp1-multitoken-fundamental-types-error.cpp2(5,8): error: 'long long unsigned int' - did you mean 'ulonglong'? |
| 14 | +pure2-cpp1-multitoken-fundamental-types-error.cpp2(5,8): error: 'long long unsigned int' - did you mean cpp2::'ulonglong'? |
15 | 15 | pure2-cpp1-multitoken-fundamental-types-error.cpp2(5,8): error: 'long long unsigned int' is an old-style C/C++ multi-word keyword type
|
16 | 16 | - most such types should be used only for interoperability with older code
|
17 | 17 | - using those when you need them is fine, but name them with these short names instead:
|
18 | 18 | short, ushort, int, uint, long, ulong, longlong, ulonglong, longdouble, __schar, __uchar
|
19 | 19 | - see also cpp2util.h > "Convenience names for integer types"
|
20 |
| -pure2-cpp1-multitoken-fundamental-types-error.cpp2(6,8): error: 'long double' - did you mean 'long'? |
| 20 | +pure2-cpp1-multitoken-fundamental-types-error.cpp2(6,8): error: 'long double' - did you mean cpp2::'long'? |
21 | 21 | pure2-cpp1-multitoken-fundamental-types-error.cpp2(6,8): error: 'long double' is an old-style C/C++ multi-word keyword type
|
22 | 22 | - most such types should be used only for interoperability with older code
|
23 | 23 | - using those when you need them is fine, but name them with these short names instead:
|
24 | 24 | short, ushort, int, uint, long, ulong, longlong, ulonglong, longdouble, __schar, __uchar
|
25 | 25 | - see also cpp2util.h > "Convenience names for integer types"
|
26 |
| -pure2-cpp1-multitoken-fundamental-types-error.cpp2(7,8): error: 'unsigned char' - did you mean 'u8' (usually best) or '__uchar'? |
| 26 | +pure2-cpp1-multitoken-fundamental-types-error.cpp2(7,8): error: 'unsigned char' - did you mean cpp2::'u8' (usually best) or '__uchar'? |
27 | 27 | pure2-cpp1-multitoken-fundamental-types-error.cpp2(7,8): error: 'unsigned char' is an old-style C/C++ multi-word keyword type
|
28 | 28 | - most such types should be used only for interoperability with older code
|
29 | 29 | - using those when you need them is fine, but name them with these short names instead:
|
|
0 commit comments