On Fri, Aug 22, 2003 at 02:30:13PM +0200, Juergen Boemmels wrote:
> a format for the line-info bytecode segement. The only question is
> reinvent the wheel, or use an already establiched format (stabs or
> DWARF).
can they do the things below?
> 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
I think that it has practical uses for other, dimensionally inferior
languages. It would often be nice to know which bit of this line:
} elsif ($host =~ /([^.]+\.[^.]{3}$)/ || $host =~ /([^.]{4,}\.[^.]{2}$)/ ) {
generated the undefined warning
Also, to be general we should do arbitrary dimensions, else the trifunge
hackers will feel left out.
> 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.
Also it would be nice to be able to record debugging lines at several levels,
so that a macro invocation can be stepped through as one line, or as each
line of the macro definition. (recursively)
It's a right pain trying to follow the perl5 C source in a C debugger, or
C++ inline code in gdb. I think that we can learn from those pain sources.
Nicholas Clark
