On 3/19/16, James K. Lowden <jklowden at schemamania.org> wrote: > > Second, you can't test the future. If the correctness of the code is > subject to change by the compiler's interpretation of the language, how > is the programmer to prevent it? >
Indeed. Every bit of the code examined by Prof. Regehr was well-defined according to K&R. But subsequent revisions of the C-language standards changed that. How does one write code that will comply with language standards that keep changing out from under you? -- D. Richard Hipp drh at sqlite.org
