使用 c# 的 StrucLayout 和 FieldOffset 表示联合位域
据我所知,为了在 C# 中表示联合,我需要使用 StructLayout[LayoutKind.Explicit)] 和 [FieldOffset(x)] 属性来指定联合内的字节偏移量。但是,我有一个想要表示的以下联合,并且 FieldOffset attrib 仅按字节大小偏移。
union _myUnion
{
unsigned int info;
struct
{
unsigned int flag1:1 // bit 0
unsigned int flag2:1 // bit 1
unsigned int flag3:1 // bit 2
unsigned int flag4:1 // bit 3
unsigned int flag5:1 // bit 4
unsigned int flag6:1 // bit 5
.
.
.
unsigned int flag31:1 // bit 31
}
}
正如您所看到的联合中的内部结构,我无法使用 FieldOffset,因为我需要可以稍微偏移的东西。
有解决办法吗?我试图调用一个 DLL 函数,并且其中一个数据结构是这样定义的,但我对如何最好地表示这个联合结构没有想法。
I understand that in order to represent unions in C# I need to use StructLayout[LayoutKind.Explicit)] and [FieldOffset(x)] attribut to specify the byte offset inside the union. However, I have a following union I want to represent and FieldOffset attrib only offset by size of a byte.
union _myUnion
{
unsigned int info;
struct
{
unsigned int flag1:1 // bit 0
unsigned int flag2:1 // bit 1
unsigned int flag3:1 // bit 2
unsigned int flag4:1 // bit 3
unsigned int flag5:1 // bit 4
unsigned int flag6:1 // bit 5
.
.
.
unsigned int flag31:1 // bit 31
}
}
As you can see for the inner struct in the union, I can't use FieldOffset since I need something that can offset by a bit.
Is there a solution to this? I am trying to call a DLL function and one of the data struct was defined as such and I ran out of ideas on how to best represent this union struct.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
是的,你可以这样做。您走在正确的道路上,答案在于使用 BitVector32 以及 FieldOffset 和 StructLayout 属性。但是,执行此操作时需要记住许多事项:
您需要显式指定包含相关数据的变量的大小。第一项非常需要注意。例如,在上面的问题中,您将 info 指定为 unsigned int。 unsigned int 的大小是多少? 32 位? 64位?这取决于运行此特定版本的 .NET 的操作系统版本(可能是 .NET Core、Mono 或 Win32/Win64)。
这是什么“字节顺序”或位顺序?同样,我们可能在任何类型的硬件上运行(想想移动/Xamarin,而不仅仅是笔记本电脑或平板电脑)——因此,您不能假设 Intel 位顺序。
我们希望避免任何依赖于语言的内存管理,或 C/C++ 术语中的 POD(普通旧数据)类型。这意味着仅坚持值类型。
我将根据您的问题和标志 0-31 的规范做出假设 sizeof(int) == 32。
诀窍是确保以下几点:
以下是我们实现这一目标的方法:
特别注意构造函数。根据定义,您不能在 C# 中为结构定义默认构造函数。但是,我们需要某种方法来确保 BitVector32 对象及其部分在使用前正确初始化。我们通过需要一个采用虚拟整数参数的构造函数来实现这一点,并像这样初始化对象:
顺便说一句,您决不限于单个位域——您可以定义您喜欢的任何大小的位域。例如,如果我要将您的示例更改为:
我只需将我的课程更改为:
关于此主题的最后一句话...很明显,只有当您绝对必须 这样做。显然,这需要对操作系统环境、运行语言、调用约定以及许多其他脆弱要求的专业知识。
在任何其他上下文中,这里都有如此多的代码味道,这显然是不可移植性的。但从你的问题的背景来看,我推测重点是你需要靠近硬件运行并且需要这种精度。
买者自负!
Yes, you can do this. You are on the right path, the answer lies in the use of BitVector32 along with the FieldOffset and StructLayout attributes. However, there are a number of things you need to keep in mind when doing this:
You need to explicitly specify the size of the variables that will contain the data in question. This first item is very important to pay attention to. In your question above, for example, you specify info as unsigned int. What size is unsigned int? 32 bits? 64 bits? That depends on the version of the OS where this particular version of .NET is running (this may be .NET Core, Mono, or Win32/Win64).
What 'endianness ' or bit order is this? Again, we may be running on any type of hardware (think Mobile/Xamarin, not just laptop or tablet) -- as such, you cannot assume Intel bit order.
We will want to avoid any memory management that is language dependent, or in C/C++ parlance POD (plain old data) types. That will mean sticking to value types only.
I'm going to make the assumption, based on your question and the specification of flags 0-31, that sizeof(int) == 32.
The trick then is to ensure the following:
Here is how we accomplish that:
Pay particular attention to the constructor. By definition, you cannot define default constructor for structs in C#. However, we need some way to ensure that the BitVector32 object and its sections are initialized properly before use. We accomplish that by requiring a constructor that takes a dummy integer parameter, and initialize the object like this:
By the way, you aren't by any means limited to single bitfields -- you can define any size bitfield you like. For example, if I were to change your example to be:
I would just change my class to be:
One last word about this topic... it should be obvious that this should only be done if you absolutely MUST do this. Clearly, this requires specialized knowledge of your OS environment, the language you are running in, your calling convention, and a host of other brittle requirements.
In any other context there are so many code smells here that this clearly screams of non-portability. But from the context of your question, I would surmise the whole point is that you need to run close to the hardware and need this kind of precision.
Caveat emptor!
那里不需要工会;数据的一个字段+属性,8 个执行按位“移位”操作的属性,例如:
等等。我还以为你想要 bool 在这里?
通常我会说:不要创建可变结构。 PInvoke可能(我不确定)是一个有效的场景,所以我会忽略它:)
如果该值确实使用超过 32 位,请考虑将支持字段切换为 ulong。
No need for union there; one field+property for the data, 8 properties that do bitwise "shift" operations, for example:
etc. I would also have thought you want bool here?
Normally I'd say: don't make mutable structs. PInvoke may (I'm not sure) be a valid scenario for that, so I'll ignore it :)
If the value is genuinely using more than 32 bits, consider switching the backing field to ulong.
最优雅的解决方案是使用标志 enum
更好地使用 uint 而不是 int
之后,您可以使用 int 作为 enum 和 uint
这通常由 PInvoke 封送
Most elegant solution for this is using flags enum
Better use uint instead int
After it you can use int as enum and as uint
This will be normally marshal by PInvoke