Variables outside the scope of declaration : CINT bug?

hi! I have a small problem : i can define a variable in an scope of a for or a if block and then it can be accesed outside of that block without any error or warning message. the behaviour its even more strange with arrays : with the exception of the last index the array it is initialised to 0 and the last element kept the previous value .
I made a small macro … i hope that i dont miss something that i should know :blush:
test2.C (420 Bytes)


This is one of the known limitation of the current CINT execution engine (scoping issues). We are working on a new engine that will solve this type
of issues.