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 pitrou
Recipients alex, fil, francismb, mark.dickinson, meador.inge, pitrou, skrah, tim.peters
Date 2013-12-09.00:38:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386549532.2291.15.camel@fsol>
In-reply-to <>
> Of course any integer length could be handled by memoryview unpacker,
> but this would not really make sense for int64. My view is that any
> intrinsic type (ie. register type) is the key point at which it should
> be supported by struct, and not a custom unpacker. 128/256/512 bit
> integers are in this category..

I don't think "register types" matter here. The struct module provides
interoperability with low-level *data types* (in C and other common
languages), not CPU *registers*.

So IMHO the question is whether there is an use case for 128-bit
integers; *not* for arrays of four 32-bit integers packed in a 128-bit
Date User Action Args
2013-12-09 00:38:55pitrousetrecipients: + pitrou, tim.peters, mark.dickinson, alex, skrah, meador.inge, francismb, fil
2013-12-09 00:38:55pitroulinkissue19904 messages
2013-12-09 00:38:55pitroucreate