On 17.07.13 11:05, Marcus Denker wrote:
What you need to do for that is to implement a class that has the same public
API as OpalCompiler and Compiler…
Then you can set this is the compiler of your class (override #compiler on the
class side).
This compiler then takes care to create the CompiledMethod with your bytecode
*and* your source.
The tools *should* be able to display just anything, but that needs to be
double-checked as we changed the tools a lot
and there is no example of methods with non-smalltalk source right now.
Thanks for the detailed steps - I think I have all the pieces now for
tackling a really crazy idea I have.
Implementing Debugger support is possible, too. For that you need to have a
mapping between pc and source for your
language.
I didn't even think of the debugger. Mapping the source I have and the
pc should be easy - although I'm not quite sure whether it's useful for
what I'm trying. But we'll see.
Udo
