Re: How to get around the "long" 32/64-bit mess?

From: Ian (noone_at_nowhere.com)
Date: 08/15/04 

Date: Sun, 15 Aug 2004 13:48:53 +1200

Adam Ierymenko wrote:
>
> So I'd like to use standard types. Is there *any* way to do this, or
> do I have to create a typedefs.h file like every cryptography or other
> integer-size-sensitive C/C++ program has to do?
>

Be explicit, use int32_t or uint32_t.

Doesn't help with endian issues, the other postings on this thread cover
that, but inside the code these fixed size types are your friend.

Ian

Relevant Pages

  • Re: Endianess
    ... to standardize by resolution. ... huge benefits of using big endian over little endian. ... Binary file parsers get written or re-written with explicit byte ...
    (comp.arch)
  • Re: Cohens paper on byte order
    ... Brian Gladman wrote: ... > Now all you have to do is to write the little endian version - the one where ... do need conversion (explicit or implicit) in data ...
    (sci.crypt)
  • Re: Transfer Syntax negotiation.
    ... Explicit VR, Little Endian ... must be both proposed by the SCU and supported by the SCP except for very specific exceptions defined in DICOM part 5. ... Since there are now talks in the DICOM committee to retire the big endian transfer syntax, this policy might change however, either to ...
    (comp.protocols.dicom)