I caught myself shortening comments because the finished program needed to be small. The source file is not going on the disk image, and apparently my brain needed that explained.
Comments are back. The variable names are still questionable.
Comments versus code size: I was solving the wrong problem
3 replies · opened 3 DAY ago
Future-you does not charge disk blocks. Write what the routine assumes, especially the state it does not restore.
My favorite comment is “temporary fix” followed by a date three years ago. Still useful, technically.
In BASIC the comments do cost memory, so I keep a readable master and generate the compact listing. Best of both worlds, plus another build step to forget.
Want to add to this transmission?
SIGN IN TO REPLY →