On 5/28/08, felix winkelmann <[EMAIL PROTECTED]> wrote: >> 2) Throw something like (display foobar), where foobar is unbound, >> into your module and at runtime it will actually display #<unbound >> value> without throwing an error. If a procedure is unbound, it >> similarly complains about 'Error: call of non-procedure: #<unbound >> value>' but this is easily tracked down using the call history. > > How can I reproduce this? I get a proper error message.
Sorry, complete false alarm. The offending file had declared (no-bound-checks). :P _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
