O
optimistx
How do you prevent your code looking cluttered?
When there are debugging statements and many kinds of error
checking statements added, the programs start looking
cluttered, difficult to read and comprehed. They do
not resemble nice and elegant school book examples.
If we remove the extra statements and save both versions,
we have two versions to maintain, and they might get
out of sync. (and final removal of debugging statements
might be bad, because later when changing the program
they would be useful to still have).
Have you found a program which would remove the extra
(or 'extra') statements marked with some rule?
Or is there a way to utilize inheritance, prototypes etc to
maintain two (or perhaps more) versions so that one
could see the short version easily, and all the changes would
go naturally where they belong without risk becoming
out of sync?
What do you think?
When there are debugging statements and many kinds of error
checking statements added, the programs start looking
cluttered, difficult to read and comprehed. They do
not resemble nice and elegant school book examples.
If we remove the extra statements and save both versions,
we have two versions to maintain, and they might get
out of sync. (and final removal of debugging statements
might be bad, because later when changing the program
they would be useful to still have).
Have you found a program which would remove the extra
(or 'extra') statements marked with some rule?
Or is there a way to utilize inheritance, prototypes etc to
maintain two (or perhaps more) versions so that one
could see the short version easily, and all the changes would
go naturally where they belong without risk becoming
out of sync?
What do you think?