Issue 5096 in pharo: Monticello uses the wrong compiler for class and trait definitions

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

Issue 5096 in pharo: Monticello uses the wrong compiler for class and trait definitions

pharo
Status: Accepted
Owner: renggli

New issue 5096 by renggli: Monticello uses the wrong compiler for class and  
trait definitions
http://code.google.com/p/pharo/issues/detail?id=5096

That was already wrong since the beginning of time, but the new solution is  
not better either. Monticello should try to use the compiler defined in the  
superclass of the class loaded, not the compiler of Monticello.


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

Re: Issue 5096 in pharo: Monticello uses the wrong compiler for class and trait definitions

pharo
Updates:
        Labels: Milestone-1.4 Type-Bug

Comment #1 on issue 5096 by renggli: Monticello uses the wrong compiler for  
class and trait definitions
http://code.google.com/p/pharo/issues/detail?id=5096

(No comment was entered for this change.)


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

Re: Issue 5096 in pharo: Monticello uses the wrong compiler for class and trait definitions

pharo

Comment #2 on issue 5096 by [hidden email]: Monticello uses the  
wrong compiler for class and trait definitions
http://code.google.com/p/pharo/issues/detail?id=5096

Do you have code?


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