> In disk.cpp:
>
>> @@ -2651,11 +2651,9 @@ int disk_empty (int num)
>>
>>  static TCHAR *tobin (uae_u8 v)
>>  {
>> -	int i;
>> -	static TCHAR buf[10];
>> -	for( i = 7; i >= 0; i--)
>> +	static TCHAR buf[9];
>> +	for (int i = 7; i >= 0; i--)
>
> yes, but you need add a special flag (-std=c99 or -std=gnu99) which can
> open a new can of worms (it's not active by default) - there's no reason
> to move the int declaration in the for statement to fix the issue at hand.

Sorry, no. I won't accept any style changes or "clean ups" that makes it 
look only nicer, most of them only make my job more difficult or 
annoying. Also this piece of code is debugging code only, no one cares.

I think you are forgetting that this is an emulator. You may do perfect 
code that does exactly what you wanted which still can be totally wrong 
because you based it on incorrect or not fully known hardware model, you 
will need to rewrite and hack it constantly. (see custom/drawing..) 
Moving variable definitions around makes it simpler and faster, it only 
wastes time (which means my free time, no one else has done any real 
core code improvements for over 5 years or more now) to make unfinished 
and experimental code look nice. Functionality always comes first.

WinUAE itself is C++ compilable (which means variable definitions can be 
anywhere = same as C99), mostly because there are some Windows libraries 
that are extremely annoying to use with plain C and glueing C and C++ 
together is also boring and annoying. C++ stuff of course stays in 
Windows-side only.