/* attempt to deal with prototype, bootstrap, jquery conflicts */ /* for dropdown menus */

Jump to content

Image of the Day

Day 17 -- a bunch more tools join the table :) #blender3d #screenshotsaturday #itssaturdaysomewhere #lowpoly #3D https://t.co/CYJucn0Lfv
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net's newsletters to receive the latest updates and exclusive content.


Sign up now

Microsoft WORD sizes

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
1 reply to this topic

#1 incertia   Members   

787
Like
1Likes
Like

Posted 10 April 2013 - 06:52 PM

I've heard that Microsoft WORD will always be 16-bit and DWORD will always be 32-bit. Is this because they change the types (say from unsigned long to unsigned short) whenever the system WORD size changes?
what

#2 L. Spiro   Members   

25026
Like
5Likes
Like

Posted 10 April 2013 - 07:06 PM

*
POPULAR

Microsoft® Visual Studio® uses the LLP64/IL32P64 data model which ensures that shorts are always 16 bits, ints and longs are always 32 bits, long long/long int are always 64 bits, etc.

 

In this case that means there is no need to change the typedef between compiler settings, but if the sizes were to change the WORD and DWORD typedefs would change to ensure their sizes remain 16- and 32- bits respectively.

 

If you are worried about sizes on Microsoft® Visual Studio® you can always use the __int16 and __int32 family of primitives.

 

 

L. Spiro






Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.