Compiler Bloat

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

H&K

Isnt it 4 bytes for the number, and four bytes pointing to where the first four bytes are?
(ie The number and a pointer?)

And if you only want 0-255, why not (as you sort of implied), just store them in string data?

And if you are realy worried about it, partition off a bit of memory, and accsess that.
Or make a 256 colour screen/picture (or just 2 colour), and just use that?
Or (Again I think you Implied), just xor 4 times.
Or if just Binary ROL and ROR, (But Imnot sure we have them)

The problem gav is talling about isnt how big the "Variables" are, but rather why some small commands make the program bigger. In particular why is

end
end
end
end

Bigger (by 4) 6K, than just End 1.5K