On Thu, Jun 21, 2007 at 12:08:33AM +0100, Jonathan Worthington wrote:
> Patrick R.Michaud (via RT) wrote:
> >The 'setline' opcode doesn't do what I expect it to do, which
> >is to associate runtime errors with lines in HLL source.
>
> Currently HLL debug info stuff is spec'd, but not implemented. Well, OK,
> the storage of it in bytecode is spec'd, the exact PIR syntax for it
> isn't. So there are two tasks: implement the underlying storage model
> for this and sort out some PIR syntax for it.
>
> How important/blocking is this to you? I can direct some tuits this way
> in the near future if you're needing it.
Well, it's not too big a block for me personally. But for
many other people who are now starting to work on testing
the perl6 compiler or building the compiler itself, it's
hugely frustrating (and I can understand that).
For example, consider something like:
$ cat foo.p6
use OtherModule; # imports some functions
my $x = 1;
bar($x);
baz($x);
Someone who runs this program gets the very cryptic:
$ ../../parrot perl6.pbc foo.p6
Null PMC access in invoke()
current instr.: 'parrot;Perl6::Compiler;main' pc 138 (perl6.pir:98)
$
This doesn't give many clues about where the program is failing
(perl6.pir:98 is the location of the rethrown exception).
So, it's important (to others) but not currently a block (to me).
I'll probably come up with a workaround in PAST.pm of some sort
in the meantime.
Personally, unless fixing this is very easy/straightforward I'd
_much_ prefer to see some of the pdd15 items completed first.
Thanks!
Pm
