Crunching code. Any tips?

[+Random Terrain]

I noticed that you can squeeze out a few extra bytes here and there by putting things on the same line, but that only works for some things. Is there a way to tell what things should be put on the same line and what doesn't help at all (or do you just have to try and find out every time)?

 

My bloated code left me with around 300 bytes free, but now I have 703 after crunching the code the best I know how. I should be able to post the rough draft of my maze-like 'game' today but it would be nice to have it crunched as much as possible first.

[+batari]

I noticed that you can squeeze out a few extra bytes here and there by putting things on the same line, but that only works for some things. Is there a way to tell what things should be put on the same line and what doesn't help at all (or do you just have to try and find out every time)?

 

My bloated code left me with around 300 bytes free, but now I have 703 after crunching the code the best I know how. I should be able to post the rough draft of my maze-like 'game' today but it would be nice to have it crunched as much as possible first.

939798[/snapback]

I can think of three ways that the generated code may be smaller after packing stuff on a single line, but all of which are technical and not really predictable at the Basic source level. So trial and error is the only way right now.

[+Random Terrain]

I can think of three ways that the generated code may be smaller after packing stuff on a single line, but all of which are technical and not really predictable at the Basic source level.  So trial and error is the only way right now.

939803[/snapback]

Thanks. Unless I skipped something, I think I tried every line that could be combined. Now I'm seeing if there is any more bloated code that I can crunch, but I am running out of ideas on how. Maybe people who are better at programming can help me crunch it more after I post it later today.