Issue 1062 in moose-technology: The GT-Debugger doesn't declare variables created while debugging
Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 1062 by v.blonde...@gmail.com: The GT-Debugger doesn't declare variables created while debugging http://code.google.com/p/moose-technology/issues/detail?id=1062
Describe the problem: what do you get? what do you expect?
When debugging, if you define a new variable in a debugged method, the variable is not declared when you save.
How to reproduce the problem: step by step if necessary
For example, debug : { 1 .2 } asOrderedCollection Go into. In the method asOrderedCollection, write: temp := self as: OrderedCollection. ^ temp
After saving, the temp variable is not declared and the method is compiled without the declaration.
Additional information: platform, context which may impact the problem
Latest Moose 5.0 - W7
Please fill in the labels with the following information: * Type-Defect * Component-GTDebugger
Comment #1 on issue 1062 by chisvasi...@gmail.com: The GT-Debugger doesn't declare variables created while debugging http://code.google.com/p/moose-technology/issues/detail?id=1062
Thanks for spotting this.
I almost fixed it, but right now the main problem is the compiler wants to report the error to a text morph. And getting the text morph from a glamour presentation is not possible. I could add a service in a text presentation that compiles some text in the context of a morph. This way the presentation just offers the compilation service, which is implemented in the renderer.
@Doru does this sound ok?
Updates: Status: Fixed
Comment #2 on issue 1062 by chisvasi...@gmail.com: The GT-Debugger doesn't declare variables created while debugging http://code.google.com/p/moose-technology/issues/detail?id=1062
(No comment was entered for this change.)
-
moose-technology＠googlecode.com