Leopold Toetsch <[EMAIL PROTECTED]> writes: > Further: > The C<setline> and C<setfile> opcodes are suboptimal, they impose > runtime penalty on each run core, so they will go finally. The > C<getline> and C<getfile> can map to the functionality used in > warnings.c.
Normal processors also don't have setline and setfile operations. They use an extra segment in the *.o file, which is only used by the debugger. This could also be done in parrot. We just need to settle on a format for the line-info bytecode segement. The only question is reinvent the wheel, or use an already establiched format (stabs or DWARF). > And finally: Parrot will (again[2]) track HLL source line info like: > > #line 17 "sourcefile.p6" > > So that warnings and errors can be located in HLL source too. It might be nice to have column information to. This would make debugging of Befunge programs a lot more easy. Also it would be nice to have blocks of code (many pasm-lines) with just one linenumber, and otherwise have a possiblity to increase the source-line with each line of pasmcode. bye boe -- Juergen Boemmels [EMAIL PROTECTED] Fachbereich Physik Tel: ++49-(0)631-205-2817 Universitaet Kaiserslautern Fax: ++49-(0)631-205-3906 PGP Key fingerprint = 9F 56 54 3D 45 C1 32 6F 23 F6 C7 2F 85 93 DD 47
