Tweet
Hi people,
There was a post recently that commented on the memory usage of comments.
I recently ran into something that kinda adds to that post:
I have a piece of code that's about 490 K as text, compiles to an EXE
of about 540K. My code was even bigger before so i wrote a little cleanup
prog that strips comments, leading spaces etc. because the IDE handles 512K text files max.
Now i found that the cleaned code compiles to an EXE that's 5K smaller than the EXE that
compiles from the code that has all the spaces and comments in it. Obviously i've checked if
my cleaner cuts away too much but that's not the case. Can anything be said about the
influence of comments/spaces on the compiled size?
The stuff i cut away is: leading spaces, empty lines (carriage return only), comments added
to a line of code (usage of ' on the same line as the code), comment lines (starting with
'), $IF 0 - $ENDIF blocks.
Thanks for anything on this.
There was a post recently that commented on the memory usage of comments.
I recently ran into something that kinda adds to that post:
I have a piece of code that's about 490 K as text, compiles to an EXE
of about 540K. My code was even bigger before so i wrote a little cleanup
prog that strips comments, leading spaces etc. because the IDE handles 512K text files max.
Now i found that the cleaned code compiles to an EXE that's 5K smaller than the EXE that
compiles from the code that has all the spaces and comments in it. Obviously i've checked if
my cleaner cuts away too much but that's not the case. Can anything be said about the
influence of comments/spaces on the compiled size?
The stuff i cut away is: leading spaces, empty lines (carriage return only), comments added
to a line of code (usage of ' on the same line as the code), comment lines (starting with
'), $IF 0 - $ENDIF blocks.
Thanks for anything on this.
Comment