[BUG] amberc: scope variable names

Hi everyone,

I would like to report a bug in amberc.

When compiling Roassal-Core [0] I had this error:

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Importing: Roassal-Core.st

an Importer>>import:

nil>>nil

a ClassCategoryReader>>scanFrom:

nil>>nil

a ClassCategoryReader>>compileMethod:

a Compiler>>install:forClass:category:

a Compiler>>compile:forClass:

a Compiler>>compile:

a Compiler>>compileNode:

an InliningCodeGenerator>>compileNode:

a SemanticAnalyzer>>visit:

a MethodNode>>accept:

a SemanticAnalyzer>>visitMethodNode:

nil>>nil

a SemanticAnalyzer>>validateVariableScope:

a SemanticAnalyzer>>errorShadowingVariable:

Variable shadowing error: elementsToRender is already defined

undefined:20917

throw anError;lk.withContext(function($ctx1) {

                                                      ^

Error:

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

The thing is that elementsToRender is an instance variable of ROView, but also the name of the argument of ROVIew>>bitmapForElements: . So, in that case I think amberc should consider the scope.

I hope it helps.

Cheers,

Pablo

[0] https://dl.dropbox.com/u/1573200/Roassal-Core.st

I actually "fixed" it just changing the name of the method's argument, but I thought that amberc behavior had to be reported.