Change line 3 of RBExtractMethodRefactoring>>extractMethod to something like: [ extractedParseTree := RBParser parseExpression: extractCode ] on: SyntaxErrorNotification do: [ :ex| ex debug ].
To bring up a debugger.
Tx this is what I was trying to do (but I should not because I was in a hacking session) and then I went to bed. I will try it. STef
Best regards, Henrik
-----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of stepharong Sent: Thursday, December 8, 2016 9:08 PM To: pharo-dev@lists.pharo.org Subject: [Pharo-dev] about syntaxError
I tried to fix the extract method refactoring that seems broken when extracting class or variables. And I wanted to understand if I can get a debugger stack instead of this useless Syntax Error: window. Now I cannot find reference to SyntaxErrorDebugger. still putting a break point in
buildMorphicViewOn: aSyntaxError "Answer an Morphic view on the given SyntaxError."
| window | self halt.
bring a debugger but with a cut stack ....
open: aSyntaxError "Answer a standard system view whose model is an instance of me." <primitive: 19> "Simulation guard" | process | process := Processor activeProcess. UIManager default spawnNewProcessIfThisIsUI: process. UIManager default defer: [ self buildMorphicViewOn: aSyntaxError. ]. ^ process suspend
so it does not really help to understand the syntax error. I do not get why this is so opaque.
Stef
-- Using Opera's mail client: http://www.opera.com/mail/
-- Using Opera's mail client: http://www.opera.com/mail/