-> The experience in the debugger is not that nice (need to think about using the <debuggerCompleteToSender> trick and explore the filtering capabilities of the debugger)
I implemented the âDebug testâ Feature again using a one-shot breakpoint. This is a good testcase to see how to improve the user experience. debugTest: aMethod (Breakpoint inNode: aMethod ast) level: nil; once. aMethod methodClass run: aMethod selector. (reflective API to create breakpoints will evolve as needed, e.g. no meta level might be the default)
I am now continuing to flesh out the Reflectivity features:
...
- add conditions with parameters (e.g. for object specific links: [:object | object == myObject])
HookGenerator now generates AST snippets for hooks with conditions that have arguments. Next: - add all reifications - code gen for the complex hooks (need to add name analysis for hooks for that) Marcus