3 ms·

> He made an error in the code: evcon. and evlis. should come before eval.. A note: That's not an error. The code works just fine in Common Lisp because CL doe

> He made an error in the code: evcon. and evlis. should come before eval.. A note: That's not an error. The code works just fine in Common Lisp because CL doesn't care about the order of definitions so long as the definitions are made prior to execution. Given that both `evcon.` and `evlis.` also call `eval.`, there is no way to create a canonical linear ordering of the three functions aside from aesthetic preference. You will get similar warnings if you put them before or put them after `eval.`.

lispm 3y ago
> The code works just fine in Common Lisp It would work fine in Lisp in general, since Lisp is typically late bound and can call global functions via the symbols. Thus in a function writing a call to an undefined function is not an error. The function only needs to exist at runtime, even then in many debuggers it could added and the computation can be resumed.