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)
Best Answer
I'm rather thinking of the word unused.
Edit: Unused should be understandable for non technical persons. Other possibilities include unnecessary (you often see this in change logs, as in removed unnecessary lines) or maybe orphaned (although I haven't seen this in a real coding situation. It's rather a translation of a term in my native tongue)