On Sunday 27 April 2008 18:08:08 Mark Glines wrote: > In the future, INTVAL will probably be 128 bits for some platforms. > I'd really like to see a set of fixed-width types (similar to what p5 > has for pack and unpack), so you have the option of "native int" or > "exactly 32 bits" or whatever you need. > > HUGEINTVAL is 64 bits on both linux-x86 and linux-amd64, so it > seems like a good start. Here's an ugly patch that attempts to add it. > > Problems with this patch: > > 1. It probably won't work on win32-x64... I seem to recall someone > mentioning HUGEINTVAL is just 32 bits there. > 2. The patch adds a HUGEINTVAL to the PObj union, and would probably > require additional fixups all over parrot to be able to access the > resulting object. > > The above makes me think we might be better off using a BigInt object > for this data. But anyway, here's what I got.
How much work is it to go the BigInt route? Just an estimate is fine right now, unless it's so easy that you can make that patch right away. -- c
