Yes, for those cases that might be possible. I was not aware that such constructions were allowed. But one still needs to move variables defined in the code like:
... int x = 10; ...
should be
int x; ... x=10; ...
since it's not known where x is used after the definition.
/ Marcus Agehall (Scanian)
Previous text:
2004-05-05 10:34: Subject: precompile.pike
You could make it to
{ int x; for(x=0;;) }
instead, which is allowed in most older C compilers too (I think -- at least Pike uses it in a lot of macros).
This will disallow (broken(?)) use of x after the for scope.
/ Mirar