Andy Wingo writes:
> On Mon 30 Jan 2012 07:39, Mark H Weaver writes:
>
>> One idea is to change 'error' into a macro, and use tricks similar to
>> what 'load' does, to cleverly makes it look like a procedure.
>
> Unfortunately this is an incompatible change. Existing compiled files
> which refe
On Mon 30 Jan 2012 07:39, Mark H Weaver writes:
> When 'error' is called, the user should _automatically_ be told the
> exact source location where it was called, and the procedure that called
> it should be present in the backtrace. Therefore, we should somehow
> prevent it from being tail-call
