It seems like erroneous code at the top-level of an .scm file fails to yield
filenames and line-numbers for backtrace/error display. For example:
echo error here > test.scm
guile --debug -l test.scm
Yields something like
Backtrace:
In unknown file:
?: 0* [primitive-load "test.scm"]
?: 1* here
<unnamed port>: In expression here:
<unnamed port>: Unbound variable: here
While
echo \(error here\) > test.scm
guile --debug -l test.scm
Yields more appropriate output:
Backtrace:
In unknown file:
?: 0* [primitive-load "test.scm"]
In test.scm:
1: 1* [error ...
test.scm:1:1: While evaluating arguments to error in expression (error
here):
test.scm:1:1: Unbound variable: here
So this seems to work correctly. I notice the primitive-load is still in an
unknown file on an unknown line, but this makes sense as it is being run
from C-code due to the -l command line argument.
Thanks in advance for your time,
Brian
====
Brian T. Crowder
Server Developer
Sony Online Entertainment
_______________________________________________
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
