On Mar 21, 2016 2:48 PM, "Scott Perry" <numist at apple.com> wrote: > > On Mar 21, 2016, at 3:17 AM, Klaas Van B. <klaasvanbe at yahoo.com> wrote: > > > >>> On 3/19/16, James K. Lowden <jklowden at schemamania.org> wrote: > > > >>> ... 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? > > > >> On Sat, 19 Mar 2016 15:50:43 -0400 Richard Hipp <drh at sqlite.org> wrote: > > > >> ... 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? > > > > It's like trying to live according to the law while they're changing the constitution. > > This is a false dichotomy. Compilers allow you to choose your standard; --std=c11 means something very specific (and unchanging) about the behaviour you can expect to be defined.
Unfortunately, gcc library header files warn about perfectly valid code in C89 mode due to changes in C99. It's not a big deal until people take compiler warnings as prima facie evidence that code is broken.
