On 09-04-2014, at 11:07 AM, Colin Putney colin@wiresong.com wrote:
On Wed, Apr 9, 2014 at 1:01 PM, tim Rowledge tim@rowledge.org wrote:
Vaguely remembered, mostly forgotten, quickly checked and claims to have cut 2Mb .. and it does indeed reduce the image size on disk. That’s also cut 7000 MCinfo-wotsits so we’re down to just 2500 (why are any left?) and a similar number of DateAndTime/Date/Time, so clearly they are tightly related. (Fun aside; inspecting MCVersionInfo allInstances, select one at random, ‘chase pointers’ - and a large list of updates start loading…. adding 13Mb to the image size. Yippee.)
That's why nobody liked it. :-)
It may be that Chris’s technique for dumping the ancestry was less than perfect, but I’d say the real problem would likely be the ancestry code. Is there any plausible reason for a ‘clean’ image to have 9000 version-doohickeys taking up a couple of MB?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: PO: Punch Operator