Re: prop_number(3) and portability of externalized plists

[David Holland <dholland-tech%netbsd.org@localhost>]

On Fri, Oct 23, 2009 at 09:25:31PM -0700, Jason Thorpe wrote:
 > > I'm bothered by the unconventional (for a Apple plists anyway) encoding
 > > of unsigned integers in externalized proplib(3) plists.
 > > 
 > > At least Python's plistlib is unequiped to handle internalizing and
 > > reexternalizing such numbers in base-16.
 > 
 > I am OK with changing to outputting base-10 always, but I would
 > like to keep the ability to internalize base-16.  I am also OK just
 > treating the number as int64_t (and thus outputting -ve numbers
 > beyond INT64_MAX).

ISTM that if there's going to be a distinction between signed and
unsigned integer values, they should be tagged differently in the XML.
Is this hopelessly naive?

-- 
David A. Holland
dholland%netbsd.org@localhost