Re: Not How it Works
Not how programmers work... I don't think it is possible to make a language where programmer oversights are not possible. For example, if a programmer thinks that only states a, b, and c are possible in a section of code, but there is a state d that he didn't think about, then there is a bug that the language can't catch. Back in the DOS days (and to a lesser extent VAX 11/780 VMS) I would sometimes create a small special purpose application or driver and I always thought about possible states of inputs and the desired states of outputs. I usually put in a check for an unexpected input state, which I would use to trigger an output of a bad input state. I gave up on any programming for Microsoft products after Windows 3.1 because it was impossible to keep track of the constantly changing APIs.