Re: GH replacement proposal (includes a bit of Unicode)

[Marius Vollmer <mvo@zagadka.de>]

prj@po.cwru.edu (Paul Jarc) writes:

>> will cause something like
>>
>>   In procedure subr1 in expression (subr1 #f):
>>   Wrong type argument: #f
>>
>> instead of
>>
>>   In procedure subr2 in expression (subr1 #f):
>>   Wrong type argument in position 1: #f
>
> Which means, if subr1 calls more than one system functions that could
> fail, I won't know what operation failed or what its arguments were,
> unless I know a lot about subr1. :(

Well, yes.  But you don't get much more information now.  Unless you
know much about subr1, knowing that the first argument to subr2 is
wrong doesn't help much.

> Could Guile provide a portable interface to walk the C stack?

That would be ideal, yes.  We already have something like it for
producing Scheme backtraces: they are done by walking the C stack, but
with help from the C code.

I'm feeling a bit uneasy about this too...

> (And would the innermost part of the C stack still be there after an
> exception?)

Yes, not after the exception but it can be gathered just before
trowing, like we do it now for the Scheme backtrace.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel