I'm a software engineer. There are many times when I write a good chunk, or even the entirety of, a feature, but opt not to make it actually run in the program for some reason or another. This code is still there, and could theoretically work, but it never will because it's inaccessible.
What's a good one-word term for such code? I want to use it, or a form of it, like this:
"This is ______ code."
"I am going to ______ this code".
Terms I considered (but don't seem to fully-convey the purpose) include:
- frozen/freeze (implies it causes the program to freeze?)
- isolated/isolate (implies it can be run in some isolated environment)
- vitrified/vitrify (implies it's changed to something else and can't change back)
- fossilized/fossilize (implies it's old and broken and should only be observed. Same problems as vitrified)
#ifdef POST_JUNE_DEVELOPMENT
. I was never sure whether that was June 94 or June 95, but it never happened (was never activated) and I removed the code in 2010. – Jonathan Leffler Apr 16 '16 at 14:23