Linked by David Adams on Tue 22nd Feb 2011 19:52 UTC, submitted by estherschindler
General Development Your company is ready to upgrade its custom applications from 32-bit to 64-bit. (Finally.) Here's 10 tips to help you make the transition as painless as possible.
Permalink for comment 464104
To read all comments associated with this story, please click here.
RE[5]: ?
by malxau on Sat 26th Feb 2011 08:58 UTC in reply to "RE[4]: ?"
Member since:

Yes, but again if you follow the API call structure you will be fine, in this case use LPARAM, WPARAM rather than what they happen to be defined as. Which is why it is important to never assume anything about API types since they can change 'behind the scenes' which can break your application if you 'assume' anything.

This triggered some long lost repressed memory. I went back to my archives, and sure enough, WPARAM/LPARAM didn't originally exist - Windows 3.0 and earlier used WORD and DWORD directly. WPARAM/LPARAM were created to facilitate the move to Win32 (where WPARAM moved from 16 to 32 bits.) But any code that predates that - and there is a surprising amount - might have just been coded with the documented and defined type, and now find itself broken.

Reply Parent Score: 2