Manuscript (Case [Issue]22440) Compiler Opal - Compiler parseExpression does not set up compilation context for method node

Classic

List

Threaded

♦

♦

Locked 1 message

Pharo Issue Tracker

Reply | Threaded

Open this post in threaded view

♦

♦

|

Manuscript (Case [Issue]22440) Compiler Opal - Compiler parseExpression does not set up compilation context for method node

Denis Kudryashov opened Case 22440: Compiler parseExpression does not set up compilation context for method node and assigned it to Marcus Denker: Bug in  Compiler Opal: 1. Pharo Image  •  You are subscribed to this case With last refactoring around parseExpression and asDoIt there was some change which loose compilation context during parse of method node. Look at OpalCompiler>>parseExpression. It should setUp "compilationContext: self compilationContext" to resulted method node. Also look at other places in RBMethodNode where context is set (RBMethodNode>>#doSemanticAnalysis). There is some dirty places which needs cleanup. I found this problem after looking at broken Seamless tests in Pharo 7. Some doIt remote scripts does not work properly there Priority: 5 – Fix If Time Status: Work Needed Assigned to: Marcus Denker Milestone: Pharo7.0 Go to Case No longer need updates? Unsubscribe from this case. Don't want Manuscript notifications anymore? Update your preferences. A Manuscript case was opened by Denis Kudryashov. Case ID: 22440 Title: Compiler parseExpression does not set up compilation context for method node Status: Work Needed Category: Bug Project: Compiler Opal Area: 1. Pharo Image Priority: 5 - Fix If Time Milestone: Pharo7.0: 02.09.2018 (Past) Assigned To: Marcus Denker URL: https://pharo.manuscript.com/f/cases/22440 With last refactoring around parseExpression and asDoIt there was some change which loose compilation context during parse of method node. Look at OpalCompiler>>parseExpression. It should setUp "compilationContext: self compilationContext" to resulted method node. Also look at other places in RBMethodNode where context is set (RBMethodNode>>#doSemanticAnalysis). There is some dirty places which needs cleanup. I found this problem after looking at broken Seamless tests in Pharo 7. Some doIt remote scripts does not work properly there You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=22440) from this case. _______________________________________________ Pharo-bugtracker mailing list [hidden email] https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker