因为这个被撞了(某种程度上)，所以有一些不同意见，所以这里有一些来自标准的相关比特。研究表明，该标准并没有真正定义前向声明，也没有明确说明枚举可以或不可以前向声明。

首先，从dcl。Enum，第7.2节:

The underlying type of an enumeration is an integral type that can represent all the enumerator values defined in the enumeration. It is implementation-defined which integral type is used as the underlying type for an enumeration 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. The value of sizeof() applied to an enumeration type, an object of enumeration type, or an enumerator, is the value of sizeof() applied to the underlying type.

因此枚举的底层类型是由实现定义的，有一个较小的限制。

接下来，我们翻到关于“不完整类型”的章节(3.9)，这是关于前向声明的最接近的标准:

A class that has been declared but not defined, or an array of unknown size or of incomplete element type, is an incompletely-defined object type. A class type (such as "class X") might be incomplete at one point in a translation unit and complete later on; the type "class X" is the same type at both points. The declared type of an array object might be an array of incomplete class type and therefore incomplete; if the class type is completed later on in the translation unit, the array type becomes complete; the array type at those two points is the same type. The declared type of an array object might be an array of unknown size and therefore be incomplete at one point in a translation unit and complete later on; the array types at those two points ("array of unknown bound of T" and "array of N T") are different types. The type of a pointer to array of unknown size, or of a type defined by a typedef declaration to be an array of unknown size, cannot be completed.

在这里，标准列出了可以前向声明的类型。Enum不存在，因此编译器作者通常认为标准不允许前向声明，因为其底层类型的大小是可变的。

这也说得通。枚举通常在按值的情况下引用，编译器确实需要知道这些情况下的存储大小。由于存储大小是实现定义的，许多编译器可能只选择为每个枚举的底层类型使用32位值，这时就可以转发声明它们。

一个有趣的实验可能是尝试在Visual Studio中向前声明枚举，然后强制它使用大于sizeof(int)的底层类型，看看会发生什么。

因为枚举可以是不同大小的整型(编译器决定给定枚举的大小)，所以指向枚举的指针也可以是不同大小的，因为它是整型类型(例如，在某些平台上字符的指针大小不同)。

所以编译器甚至不能让你前向声明枚举并使用指向它的指针，因为即使在那里，它也需要枚举的大小。

可以将枚举包装在结构体中，添加一些构造函数和类型转换，然后前向声明结构体。

#define ENUM_CLASS(NAME, TYPE, VALUES...) \
struct NAME { \
    enum e { VALUES }; \
    explicit NAME(TYPE v) : val(v) {} \
    NAME(e v) : val(v) {} \
    operator e() const { return e(val); } \
    private:\
        TYPE val; \
}

这似乎是有效的: http://ideone.com/TYtP2

[我的答案是错误的，但我把它留在这里，因为评论很有用]。

前向声明枚举是非标准的，因为指向不同枚举类型的指针不能保证大小相同。编译器可能需要查看定义才能知道该类型可以使用哪些大小指针。

实际上，至少在所有流行的编译器上，指向枚举的指针的大小是一致的。例如，枚举的前向声明是由Visual c++作为语言扩展提供的。

enum不能被前向声明的原因是，如果不知道值，编译器就不能知道enum变量所需的存储空间。c++编译器可以根据包含所有指定值所需的大小指定实际存储空间。如果所有可见的都是前向声明，那么翻译单元就不能知道所选择的存储大小是什么——它可能是char型、int型或其他类型。

ISO c++标准第7.2.5节:

The underlying type of an enumeration is an integral type that can represent all the enumerator values defined in the enumeration. It is implementation-defined which integral type is used as the underlying type for an enumeration 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. The value of sizeof() applied to an enumeration type, an object of enumeration type, or an enumerator, is the value of sizeof() applied to the underlying type.

由于函数的调用者必须知道参数的大小才能正确地设置调用堆栈，因此枚举列表中的枚举数必须在函数原型之前知道。

更新:

在c++ 0X中，已经提出并接受了向前声明enum类型的语法。你可参阅前向申报枚举数(修订版3)的建议

因为这个被撞了(某种程度上)，所以有一些不同意见，所以这里有一些来自标准的相关比特。研究表明，该标准并没有真正定义前向声明，也没有明确说明枚举可以或不可以前向声明。

首先，从dcl。Enum，第7.2节:

The underlying type of an enumeration is an integral type that can represent all the enumerator values defined in the enumeration. It is implementation-defined which integral type is used as the underlying type for an enumeration 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. The value of sizeof() applied to an enumeration type, an object of enumeration type, or an enumerator, is the value of sizeof() applied to the underlying type.

因此枚举的底层类型是由实现定义的，有一个较小的限制。

接下来，我们翻到关于“不完整类型”的章节(3.9)，这是关于前向声明的最接近的标准:

A class that has been declared but not defined, or an array of unknown size or of incomplete element type, is an incompletely-defined object type. A class type (such as "class X") might be incomplete at one point in a translation unit and complete later on; the type "class X" is the same type at both points. The declared type of an array object might be an array of incomplete class type and therefore incomplete; if the class type is completed later on in the translation unit, the array type becomes complete; the array type at those two points is the same type. The declared type of an array object might be an array of unknown size and therefore be incomplete at one point in a translation unit and complete later on; the array types at those two points ("array of unknown bound of T" and "array of N T") are different types. The type of a pointer to array of unknown size, or of a type defined by a typedef declaration to be an array of unknown size, cannot be completed.

在这里，标准列出了可以前向声明的类型。Enum不存在，因此编译器作者通常认为标准不允许前向声明，因为其底层类型的大小是可变的。

这也说得通。枚举通常在按值的情况下引用，编译器确实需要知道这些情况下的存储大小。由于存储大小是实现定义的，许多编译器可能只选择为每个枚举的底层类型使用32位值，这时就可以转发声明它们。

一个有趣的实验可能是尝试在Visual Studio中向前声明枚举，然后强制它使用大于sizeof(int)的底层类型，看看会发生什么。