forked from OSchip/llvm-project
c90e198107
Previously we implemented non-standard disambiguation rules to distinguish an enum-base from a bit-field but otherwise treated a : after an elaborated-enum-specifier as introducing an enum-base. That misparses various examples (anywhere an elaborated-type-specifier can appear followed by a colon, such as within a ternary operator or _Generic). We now implement the C++11 rules, with the old cases accepted as extensions where that seemed reasonable. These amount to: * an enum-base must always be accompanied by an enum definition (except in a standalone declaration of the form 'enum E : T;') * in a member-declaration, 'enum E :' always introduces an enum-base, never a bit-field * in a type-specifier (or similar context), 'enum E :' is not permitted; the colon means whatever else it would mean in that context. Fixed underlying types for enums are also permitted in Objective-C and under MS extensions, plus as a language extension in all other modes. The behavior in ObjC and MS extensions modes is unchanged (but the bit-field disambiguation is a bit better); remaining language modes follow the C++11 rules. Fixes PR45726, PR39979, PR19810, PR44941, and most of PR24297, plus C++ core issues 1514 and 1966. |
||
|---|---|---|
| .. | ||
| analyzer | ||
| demo | ||
| OpenProjects.html | ||
| UniversalDriver.html | ||
| builtins.py | ||
| carbon-compile.png | ||
| clang_video-05-25-2007.html | ||
| clang_video-07-25-2007.html | ||
| compatibility.html | ||
| content.css | ||
| cxx_compatibility.html | ||
| cxx_dr_status.html | ||
| cxx_status.html | ||
| diagnostics.html | ||
| favicon.ico | ||
| feature-compile1.png | ||
| feature-compile2.png | ||
| feature-memory1.png | ||
| features.html | ||
| get_involved.html | ||
| get_started.html | ||
| hacking.html | ||
| index.html | ||
| libstdc++4.4-clang0x.patch | ||
| libstdc++4.6-clang11.patch | ||
| libstdc++4.7-clang11.patch | ||
| make_cxx_dr_status | ||
| menu.css | ||
| menu.html.incl | ||
| related.html | ||
| robots.txt | ||
