Issue 4660 in pharo: Safety measure in compiler , by Eliot

Status: Accepted
Owner: [hidden email]
Labels: Milestone-1.4

New issue 4660 by [hidden email]: Safety measure in compiler , by Eliot
http://code.google.com/p/pharo/issues/detail?id=4660

Name: Compiler-eem.212
Author: eem
Time: 18 August 2011, 4:32:55.72 pm
UUID: 7aa3630c-0547-4f85-821b-c1a9bb4dbbd5
Ancestors: Compiler-eem.211

Add a useful validation check to the closure analysis.  Insist
that local variables have at most one defining scope.

=============== Diff against Compiler-eem.211 ===============

Item was changed:
  ----- Method: TempVariableNode>>definingScope: (in category 'code  
generation (closures)') -----
  definingScope: scopeBlock "<BlockNode>"
+       definingScope ifNotNil:
+               [self error: 'temp has more than one defining scope.  This  
is probably a parser error'].
        definingScope := scopeBlock!



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixProposed

Comment #1 on issue 4660 by [hidden email]: Safety measure in  
compiler , by Eliot
http://code.google.com/p/pharo/issues/detail?id=4660

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #2 on issue 4660 by [hidden email]: Safety measure in  
compiler , by Eliot
http://code.google.com/p/pharo/issues/detail?id=4660

in 14099


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker