模板函数特化问题
我正在使用模板来实现从 int 到 enum 的范围检查转换。它看起来像这样:
template<typename E>
E enum_cast(const int &source);
模板函数或多或少地放置在项目的根目录中。当定义一个新的枚举时,预计会从配置文件中分配值,如下所示:
enum ConfigEnum {
ConfigEnumOption1 = 'A'
, ConfigEnumOption2 = 'B'
, ConfigEnumInvalid };
ConfigEnum option = XmlNode.iAttribute("option");
我在使用此枚举的模块的 .cpp 文件中为该特定枚举类型定义了一个模板专门化。
template<>
ConfigEnum enum_cast(const int &source) {
switch(source) {
case ConfigEnumOption1 : return ConfigEnumOption1;
case ConfigEnumOption2 : return ConfigEnumOption2;
default return ConfigEnumInvalid;
}
现在分配一个 int到枚举变为:
ConfigEnum option = enum_cast<ConfigEnum>(XmlNode.iAttribute("option"));
这确保枚举始终在有效范围内。请注意,我并不总是控制这些枚举,因此这似乎是一个合理且易于配置的解决方案。
不管怎样,这一切都很好(尽管我不确定这里给出的所有代码都是正确的,因为我现在只是从记忆中回忆起它)
问题源于这样一个事实,即可能需要在整个代码中使用这个“enum_cast”构造每当将 in 分配给枚举时。毕竟这可以通过简单的搜索和替换操作来强制执行。当然,我不想为所有枚举定义这些专业化,而只想为那些目前需要范围检查的枚举定义这些专业化。我更愿意在需要时为枚举类型添加模板专业化,并在未定义专业化时使用赋值运算符。
因此:
InternalEnum internal = enum_cast<InternalEnum>(internal_integer);
将有效地调用内部=内部_整数。我认为我需要告诉编译器对所有没有专门化的枚举类型使用某种“默认”实现。
我的第一个赌注是为原始模板函数提供这样的实现:
template<typename E>
E enum_cast(const int &source) {
E copy = source;
return copy;
};
不幸的是,现在总是调用它,而不是在项目目录树更深处的 .cpp 文件中给出的专业化。
有什么想法吗?
提前致谢 阿内
I am using templates to implement a range checked conversion from int to enum. It looks like this:
template<typename E>
E enum_cast(const int &source);
The template function placed more or less in the root-directoy of the project. When defining a new enum that is foreseen to be assigned values from a config file like this:
enum ConfigEnum {
ConfigEnumOption1 = 'A'
, ConfigEnumOption2 = 'B'
, ConfigEnumInvalid };
ConfigEnum option = XmlNode.iAttribute("option");
I define a template specialization for this particular enum type in a .cpp-file for the module this enum is used in.
template<>
ConfigEnum enum_cast(const int &source) {
switch(source) {
case ConfigEnumOption1 : return ConfigEnumOption1;
case ConfigEnumOption2 : return ConfigEnumOption2;
default return ConfigEnumInvalid;
}
Now the assignment of an int to the enum becomes:
ConfigEnum option = enum_cast<ConfigEnum>(XmlNode.iAttribute("option"));
which makes sure that the enum is allways in valid range. Note that I have not allways control over these enums so this seems to a be reasonable and easily configureable solution.
Anyway, this works all very well (although I am not shure all code given here is correct because I just recall it from memory right now)
The problem stems from the fact that it might be desireable to use this "enum_cast" construct thorughout the code base whenever an in is assigned to a enum. After all this can be enforced by a simple search-and-replace operation. Of course I do not want to define these specializations for all and every enum around but only for those that need the range check at the moment. I would prefer to add template specializations for the enum types when the need arises and use the assignment operator when no specialization is defined.
Thus:
InternalEnum internal = enum_cast<InternalEnum>(internal_integer);
would effecively call internal = internal_integer. I figure that I need to tell the compiler to use a certain "default" implementation for all enum types that do not have a specialization.
My first bet was giving the original template function an implementation like this:
template<typename E>
E enum_cast(const int &source) {
E copy = source;
return copy;
};
Unfortunately now this is allways called instead of the specialiazations given in the .cpp-files deeper into the project directory-tree.
Any thoughts?
Thanks in advance
Arne
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
显式专业化必须在使用它们的任何地方都可见。由于它们是定义,因此它们不能在每个编译单元中重复。因此,在定义枚举的头文件中,您要检查您所说的内容
,并在相应的 .cpp 中给出定义。
The explicit specializations have to be visible everywhere they are used. And as they are definitions, they can't be repeated in every compilation unit. So in the header file where you define an enum you want to check you say
and in the corresponding .cpp you give the definition.
您不能使用特征类来描述每个枚举吗:
通常枚举定义伴随着 EnumTraits 专业化。对于您无法控制的任何枚举,边界检查仅使用默认特征。
Couldn't you use a traits class to describe each enum:
Normally the enum definition is accompanied by an EnumTraits specialisation. For any enums outside your control then the bounds checking just uses the default traits.
这
适用于我的机器(TM)。它打印
This
Works On My Machine(TM). It prints