Preprocessor directives can be corrupted by newly generated scopes about c99-to-c89 HOT 3 CLOSED

I think I did the original "place closing bracket on same line as statement causing it" just so line numbers wouldn't change too much. I don't mind at all if we just add a newline before each inserted closing bracket.

from c99-to-c89.

I think that in this particular case the tool considers lines
int b;
#line 1 "D:\qwe.c"
as one block that requires a new scope. So the closing brace is inserted at the end of the second line.
Inserting a newline before the brace, in my opinion, is not the best option as it will change the line numbers. It will break the debug for those people who use the tool for code instrumentation as an intermediate step (just as I do in my project).
So as proposed in my fix we can insert the bracket right on the next line if the firstly intended line is not a complete statement (ends with ";" or "}").

from c99-to-c89.

That's fine also. I always had this long-term idea that I'd insert #line directives through this tool to maintain original line numbers in the MSVC debugger, but that never happened so ... ohwell.

from c99-to-c89.