"The code is the spec."
This is the source of the problem. It was a shortcut, but one that has costs long term.
Justus is right about that.
Until the code is frozen/deprecated and we have an functional spec, we will have this quandry.
i read about this here one time but i don't fully understand it nor the implications, not being a coder.
a spec is a written, detailed, normal language description of how the protocol works, is that correct? wouldn't the current developer's guide qualify as something similar?
where as the code is what actually executes within the operating system and carries out the protocol rules?
and why NL, do you believe it would've prevented what we have going on now?