枚举与具有静态成员的常量/类？

发布于 2024-11-06 19:21:08 字数 288 浏览 0 评论 0原文

我有一组特定于应用程序的代码（代码与其名称的一对一映射），并且我一直在 C# 中使用枚举来表示它们。我现在不确定这是否有必要。这些值永远不会改变，并且它们总是与这些标签相关联：

Workflow_Status_Complete = 1
Workflow_Status_Stalled = 2
Workflow_Status_Progress = 3
Workflow_Status_Complete = 4
Workflow_Status_Fail = 5

我应该使用枚举还是具有静态成员的类？

原文

I have a set of codes that are particular to the application (one to one mapping of the code to its name), and I've been using enums in C# to represent them. I'm not sure now if that is even necessary. The values never change, and they are always going to be associated with those labels:

Workflow_Status_Complete = 1
Workflow_Status_Stalled = 2
Workflow_Status_Progress = 3
Workflow_Status_Complete = 4
Workflow_Status_Fail = 5

Should I use an enum or a class with static members?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

骄傲 2024-11-13 19:21:08

对我来说，int 类型的静态成员似乎不如枚举。你失去了枚举的类型安全性。调试时您看不到符号名称，而只是一个数字。

另一方面，如果条目不仅仅包含名称/整数值对，那么类可能是一个好主意。但这些字段应该是该类的而不是 int 的。像这样的东西：

class MyFakeEnum
{
   public static readonly MyFakeEnum Value1=new MyFakeEnum(...);
}

Static members of type int seems to be inferior to an enum to me. You lose the typesafety of an enum. And when debugging you don't see the symbolic name but just a number.

On the other hand if an entry consists of more than just a name/integervalue pair a class can be a good idea. But then the fields should be of that class and not int. Something like:

class MyFakeEnum
{
   public static readonly MyFakeEnum Value1=new MyFakeEnum(...);
}

回复收藏 0 原文

ぃ弥猫深巷。 2024-11-13 19:21:08

使用枚举。即使您的代码从未改变，仅通过检查也很难知道该值代表什么。使用枚举的众多优点之一。

enum RealEnum : uint
{
    SomeValue = 0xDEADBEEF,
}
static class FakeEnum
{
    public const uint SomeValue = 0xDEADBEEF;
}

var x = RealEnum.SomeValue;
var y = FakeEnum.SomeValue;
// what's the value?
var xstr = x.ToString(); // SomeValue
var ystr = y.ToString(); // 3735928559

即使是调试器也无法为您提供太多帮助，尤其是在有许多不同值的情况下。

Use an enum. Even though your codes never change, it will be difficult to know what the value represents just by inspection. One of the many strengths of using enums.

enum RealEnum : uint
{
    SomeValue = 0xDEADBEEF,
}
static class FakeEnum
{
    public const uint SomeValue = 0xDEADBEEF;
}

var x = RealEnum.SomeValue;
var y = FakeEnum.SomeValue;
// what's the value?
var xstr = x.ToString(); // SomeValue
var ystr = y.ToString(); // 3735928559

Not even the debugger will help you much here, especially if there are many different values.

回复收藏 0 原文