lParam和wParam

最新推荐文章于 2024-03-31 08:00:00 发布

原创最新推荐文章于 2024-03-31 08:00:00 发布 · 905 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

C/C++ 同时被 2 个专栏收录

154 篇文章

订阅专栏

windows

67 篇文章

订阅专栏

本文深入解析了Windows消息参数WPARAM、LPARAM和LRESULT的起源及其在不同位宽系统间的转换规则，解释了它们在传递不同类型数据时的作用，并详细说明了在32位与64位系统中参数宽度的变化。

Once upon a time, Windows was 16-bit. Each message could carry with it two pieces of data, called WPARAM and LPARAM. The first one was a 16-bit value ("word"), so it was called W. The second one was a 32-bit value ("long"), so it was called L.

You used the W parameter to pass things like handles and integers. You used the L parameter to pass pointers.

When Windows was converted to 32-bit, the WPARAM parameter grew to a 32-bit value as well. So even though the "W" stands for "word", it isn't a word any more. (And in 64-bit Windows, both parameters are 64-bit values!)

It is helpful to understand the origin of the terms. If you look at the design of window messages, you will see that if the message takes a pointer, the pointer is usually passed in the LPARAM, whereas if the message takes a handle or an integer, then it is passed in the WPARAM. (And if a message takes both, the integer goes in the WPARAM and the pointer goes in theLPARAM.)

Once you learn this, it makes remembering the parameters for window messages a little easier. Conversely, if a message breaks this rule, then it sort of makes your brain say, "No, that's not right."

//------------

The integral types WPARAM, LPARAM, and LRESULT are 32 bits wide on 32-bit systems and 64 bits wide on 64-bit systems. What happens when a 32-bit process sends a message to a 64-bit window or vice versa?

There's really only one choice when converting a 64-bit value to a 32-bit value: Truncation. When a 64-bit process sends a message to a 32-bit window, the 64-bit WPARAM and LPARAM values are truncated to 32 bits. Similarly, when a 64-bit window returns an LRESULT back to a 32-bit sender, the value is truncated.

But converting a 32-bit value to a 64-bit value introduces a choice: Do you zero-extend or sign-extend?

The answer is obvious if you remember the history of WPARAM, LPARAM, and LRESULT, or if you just look at the header file.

The WPARAM is zero-extended, while LPARAM and LRESULT are sign-extended.

If you remember that WPARAM used to be a WORD and LPARAM and LRESULT used to be LONG, then this follows from the fact that WORD is an unsigned type (therefore zero-extended) and LONG is a signed type (therefore sign-extended).

Even if you didn't know that, you could look it up in the header file.

typedef UINT_PTR WPARAM;
typedef LONG_PTR LPARAM;
typedef LONG_PTR LRESULT;

UINT_PTR is an unsigned type (therefore zero-extended) and LONG_PTR is a signed type (therefore sign-extended).