Because I'm spending a lot of time looking at source code on the Helio, I've been trying to figure out how I can keep comments in the system. I think the normal SqueakV2.sources is a little big to be carting around, so I did a condenseSources on a majorShrink'd image, and ended up with a 2M sources file. Is condenseSources considered to be Evil? Should I not be thinking about this?
The 2M compressed down pretty nicely. Zip got it to like 430k. It's a pain to seek around in a big compressed file, so I split it into 64k chunks and then compressed those; ended up around 510k. Does anyone already have Squeak code to read such an indexed collection of compressed chunks?
510k isn't much to pay in ramdisk on an 8M machine.
Jay
Ok, I'm curious, if you remove the comments from the source, how much space do you get back (IE in the sources file, how much is code, how much is comments)
Just a thought (64k here 64k there, all of a sudden no space left)
On Thu, 2 Nov 2000, John M McIntosh wrote:
Ok, I'm curious, if you remove the comments from the source, how much space do you get back (IE in the sources file, how much is code, how much is comments)
Sum of all method's source code size: 8044462 Sum of all comment's length in there: 1837882
-- Bert
On Thu, 2 Nov 2000, John M McIntosh wrote:
Ok, I'm curious, if you remove the comments from the source, how much space do you get back (IE in the sources file, how much is code, how much is comments)
and Henrik replied...
Sum of all method's source code size: 8044462 Sum of all comment's length in there: 1837882
A reasonable thing to do would be to store comments only, with indices as to where to insert them into the decompiler's output. From the above stats, this would appear to give you better than a four-fold savings in source code storage space.
- Dan
squeak-dev@lists.squeakfoundation.org