It is most common to use 4 bytes to store an integer value, even if
the full range will not be used. There is no problem putting a 16-bit
value into a 32-bit field. The only case where this is not true is
when memory is extremely limited and you need to pack as much into
every word as possible. Do
@don: so if a 16bit value is put into a 32 bit field and i need to read the
value, do i need to read last 16 bits only somehow ?
On Wed, Aug 24, 2011 at 8:22 PM, Don dondod...@gmail.com wrote:
It is most common to use 4 bytes to store an integer value, even if
the full range will not be used.
On Aug 24, 11:41 pm, Arun Vishwanathan aaron.nar...@gmail.com wrote:
@don: so if a 16bit value is put into a 32 bit field and i need to read the
value, do i need to read last 16 bits only somehow ?
As long as you are saving those 16 bits in a variable (an integer, a
bit-field or
On Thu, Aug 25, 2011 at 2:04 AM, Ninad Page ninad1...@gmail.com wrote:
If you stick to one convention its not that difficult to code without
bothering about endian's.In your case if you want to have a variable data
size for int(As far as I can guess),develop ur own integer interface using
raw
