This has been standardized, proposal 2764: Forward declaration of enumerations (rev. 3) allowed the forward declaration of enums if you specify the underlying type, whereas before this was not possible.
The main reason is that when the underlying type is not specified the size is implementation defined and can depend on the enumerator values. From the draft C++11 standard section 7.2
[dcl.enum]:
For an enumeration whose underlying type is not fixed, the underlying
type is an integral type that can represent all the enumerator values
defined in the enumeration. If no integral type can represent all the
enumerator values, the enumeration is ill-formed. It is
implementation-defined which integral type is used as the underlying
type except that the underlying type shall not be larger than int
unless the value of an enumerator cannot fit in an int or unsigned
int. If the enumerator-list is empty, the underlying type is as if the
enumeration had a single enumerator with value 0.
When passing by value it makes sense that not knowing the underlying type is an issue, but why is it an issue when it is a pointer or reference? This matters since apparently on some architectures, char* and int* can have different sizes as mentioned in this comp.lang.c++ discussion: GCC and forward declaration of enum:
[...] While on most architectures it may not be an issue, on some
architectures the pointer will have a different size, in case it is a
char pointer. So finally our imaginary compiler would have no idea
what to put there to get a ColorsEnum*[...]
We have the following stackoverflow answer for reference which describes the case where char* can be larger than int*, which backs up the assertion in the discussion above.
Some more details on the possible sizes of pointers it looks like char *
and void *
are the two main exceptions here and so other object pointers should not have the same issues. So it seems like this case ends up being unique to enums.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…