Ok, just multiply that number by 10, and you have an estimate of the number of bytes consumed by the result. :) Each integer, as a rebol value, consumes around 10 bytes, if I remember correctly. So it is a fair whack of memory.
Anton. > I'm writing a set of unit tests for the compact-decompact functions for > the Rebol Library. I try to include "boundary" conditions in the tests. > One of the tests is: decompact [1x2147483646]. When I try this with > Romano's decompact Rebol goes into a tight loop that i cannot break out > of with escape and have to resort to ctrl-c. This happens both under > Core 2.6.2 and Core 2.5.6 > > Is this a bug in Rebol? > > Peter -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
