Message71110
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. |
|
Date |
User |
Action |
Args |
2008-08-14 07:18:46 | loewis | set | recipients:
+ loewis, gvanrossum, rhettinger, jcea, hniksic, alexandre.vassalotti, benjamin.peterson |
2008-08-14 07:18:45 | loewis | set | messageid: <1218698325.95.0.470407425672.issue2389@psf.upfronthosting.co.za> |
2008-08-14 07:18:30 | loewis | link | issue2389 messages |
2008-08-14 07:18:29 | loewis | create | |
|