This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients alexandre.vassalotti, benjamin.peterson, gvanrossum, hniksic, jcea, loewis, rhettinger
Date 2008-08-14.07:18:28
SpamBayes Score 8.6345266e-05
Marked as misclassified No
Message-id <1218698325.95.0.470407425672.issue2389@psf.upfronthosting.co.za>
In-reply-to
Content
I think changing the array constructor is fairly easy: just pick a set
of codes that are defined to be platform-neutral (i.e. for each size two
codes, one for each endianness). For example, the control characters
(\0..\x1F) could be used in the following way:

char, signed-byte, unsigned byte: c, b, B
(big/little)
sint16: 1,2 uint16: 3,4
sint32: 5,6 uint32: 7,8
sint64: 9,10 uint64: 11,12
float:  13,14 double: 15,16
UCS-2:  17,18 UCS-4: 19,20

In above scheme, even codes are little-endian, odd codes are big endian.
Converting the codes to "native" codes could be table-driven.
History
Date User Action Args
2008-08-14 07:18:46loewissetrecipients: + loewis, gvanrossum, rhettinger, jcea, hniksic, alexandre.vassalotti, benjamin.peterson
2008-08-14 07:18:45loewissetmessageid: <1218698325.95.0.470407425672.issue2389@psf.upfronthosting.co.za>
2008-08-14 07:18:30loewislinkissue2389 messages
2008-08-14 07:18:29loewiscreate