Compiler bug or C standard change?

DDE, C compiler version 5.82 (3rd April 2020).

The following code compiles without any warning:

   if ( poll->data.mouse.icon != -1 )
   {
      // Yes, so do something with it
      window_claimfocus(calcwin);
      iconblock *icn = (iconblock *)calcwin->icons[poll->data.mouse.icon];
      appcalc_process(icn->data[0]);
   }

The problem? I had a fat fingered moment (sadly, I can’t blame alcohol) and stuck the call to window_claimfocus() before the local declaration.

Surely declarations used in a block of code should come first?

Surely declarations used in a block of code should come first?

That’s only true for old C versions, starting with IIRC C99 declarations can be made anywhere within a block.

starting with IIRC C99 declarations can be made anywhere within a block.

Gee, it’s like BASIC then. ;-)

ignoring the rest, coding to the rules of ANSI C.

I’m more or less the same. I like the // comments, and something the for (int blah=... syntax is useful, but otherwise it’s pretty much traditional C for me (and, if I can help it, none of that _near and _far crap either, so glad that processor-specific piece of brain damage never made it into a standard).

Me, I just take advantage of inline and // comments, ignoring the rest, coding to the rules of ANSI C.

Another useful feature in C99 is macro ellipsis.
Regarding C++ style comments (//), I don’t remember any C compiler that I used that didn’t support them.
One C++ feature that I would have liked to see integrated in C would be the ability to extend structures so as to avoid having to introduce an extra structure level.