He lost me when he said "Where" 
Wednesday, August 31, 2005 10:44 AM
LarryOsterman Where do "checked" and "free" come from?
People who have MSDN or the DDK know that Windows is typically built in two different flavors, "Checked" and "Free". The primary difference between the two is that the "checked" build has traces and asserts, but the free build doesn't.
Where did those names "checked" and "free" come from? It's certainly not traditional, the traditional words are "Debug" and "Retail" (or "Release").
When we were doing the initial development of Windows NT, we started by using the same "Debug" and "Retail" names that most people use.
The thing is, it turns out that there are actually four different sets of options that make up the "Debug" and "Retail" split.
You have:
- Compiler Optimization: On/Off
- Debug Traces: On/Off
- Assertions: Enabled/Disabled
- Sanity checks: Enabled/Disabled
Traditionally, "Debug" is "Optimization
ff, Traces
n, Assertions: on" and "Retail" is "Optimization
n, Traces
ff, Assertions: off". Sanity checks was something the NT team added. The idea was that there would be additional sanity checks built in for our internal development that would be removed before we shipped.
So the NT build team wanted to build "Optimization
n, Traces
n, Assertions: on, sanity checks
n" and "Optimizations
n, traces
ff, assertions: off, sanity checks: on" and "optimizations
n, traces
ff, assertions
ff, sanity checks: off".
The last was what was traditionally called "Retail" - no debugging whatsoever. However, the question still remained - what to call the "O
n, T
n, A
n, S
n" and "O
n, T
ff, A
ff, S
n" build - the first wasn't "Debug" because the optimizer was enabled, the latter wasn't "Retail", since the sanity checks were enabled.
So clearly there needed to be some other name to differentiate these cases. After some internal debate, we settled on "Checked" for the "O
n, T
n, A
n, S
n" and "Free" for the "O
n, T
ff, A
ff, S
n" build. Checked because it had all the checks enabled, and free because it was "check free".
And as the NT 3.1 project progressed, the team eventually realized that (a) since they'd never actually tested the "retail" build, they had no idea what might break when they started making builds, and (b) since they had perf tested the free build and it met the perf criteria, the team eventually decided to ship the free build as the final version.
