proposed fix for issue 913

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

proposed fix for issue 913

Dale


http://code.google.com/p/pharo/issues/detail?id=913

I wasn't able to directly reproduce the problem in my tests, but upon code inspection
it was obvious that an empty Dictionary should be returned by
BytecodeEncoder>>blockExtentsToTempRefs instead of nil. None of the senders would be
adversely affected by the change.

Of course the changes are in the Compiler package, so it's worth having an extra set of eyes take a look.

Dale

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: proposed fix for issue 913

Stéphane Ducasse
Thanks dale.

We will doing some fixes with lukas and tomorrow there is the sprint :)

Stef

>
>
> http://code.google.com/p/pharo/issues/detail?id=913
>
> I wasn't able to directly reproduce the problem in my tests, but  
> upon code inspection
> it was obvious that an empty Dictionary should be returned by
> BytecodeEncoder>>blockExtentsToTempRefs instead of nil. None of the  
> senders would be
> adversely affected by the change.
>
> Of course the changes are in the Compiler package, so it's worth  
> having an extra set of eyes take a look.
>
> Dale
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


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