while debugging partcl, leo asked will for some source comments to understand where the generated code came from. i thought it should be possible to walk the chain from the code emitter, and print the calling sub's filename and line number in PIR.
walking the call chain is possible using a ParrotInterpreter PMC, however, the Sub PMC isn't able to get file and line info. in order to do this, the Sub PMC needs two new methods, which i propose we call 'get_file' and 'get_line'. does this seem appropriate? are these method names acceptable? if so, i'm pretty sure it can be implemented shortly, and should allow hll compilers to emit better debugging information. ~jerry