And version control keeps it around for you anyways.
I can't even count the number of times I've heard "but this code will be useful if/when we add support for feature X" used to justify hundreds or even thousands of lines of ifdeffed-out cruft.
I can't even count the number of times I've heard "but this code will be useful if/when we add support for feature X" used to justify hundreds or even thousands of lines of ifdeffed-out cruft.
if (false) { ... large incomprehensible code block .. }
was common. Why comment out stuff when you can just disable it programmatically? > This avoids archeology on historical versions.
It's not really your main point, but the idea of revision control archeology is a really a great analogy.Version control is not so easy to search, particularly if you're looking for a utility that you think is live in the project.