Re: What is the right way to print a UINTN?

["Kinney, Michael D" <michael.d.kinney@intel.com>]

Eugene,

I agree.  There are use cases for using UINTN so values can scale to CPU arch.

Casting those specific use cases from UINTN to UINT64 when used in a print call 
is likely the safest method.

There are many use case of UINTN where the value is limited to 32-bits, and
a typecast is not required.

The format specifier idea is interesting.  I need to lookup the ANSI C versions
of those.  Looks like they were introduced in C99.

Mike


> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Cohen, Eugene
> Sent: Tuesday, September 27, 2016 12:29 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; afish@apple.com
> Cc: Alexei Fedorov <Alexei.Fedorov@arm.com>; edk2-devel@lists.01.org <edk2-
> devel@ml01.01.org>; Laszlo Ersek <lersek@redhat.com>
> Subject: Re: [edk2] What is the right way to print a UINTN?
> 
> MIke,
> 
> > Portable sources that use type UINTN must never use values larger
> > than
> > 32-bits.  Same for type INTN.  Only use values in signed 32-bit range.
> 
> If the value is something like an enumeration or bitmask then I agree, but not if it's
> something numeric that is supposed to scale to larger numbers on 64-bit platforms like
> the Length field of CopyMem.
> 
> I like the proposals to use a custom format specifier (although the concatenated string
> with macro will take some getting used to).
> 
> Thanks,
> 
> Eugene
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel