Jason Eisner

Oh right, I ran into that too. On Tue, Jun 18, 2013 at 12:04 PM, Tim Vieira [email protected]: > ... and multi-line aren't handled correctly. > > — > Reply...

entertaining ...

p.s. I really like this design and this presentation of it. I got close to it in inference2.tex, where I played around with a couple of variants. But this version...

> The right way to implement `||` is ... Or, just define it as a built-in with non-standard behavior. We already have `?foo` as such a non-standard built-in: like `foo...

> Priority? How hard is it to implement? It would be nice for the tutorial, and for giving students more leeway to play around without getting into trouble the way...

So let's wait until we are farther along on indirect evaluation (or special forms) until we try this. The alternative, as I mentioned, is to transform `||` out of the...

### Other operators with special handling of nulls and errors **The if-then-else operator.** The "branch not taken" is allowed to be null or `$error` without corrupting the branch that is...

_Remark:_ Some versions of LISP used basically the trick that we are using here: that some functions (defined with `nlambda` instead of `lambda`) suppress the usual automatic evaluation of their...

Correction: Just a conjunct `is_bool(X)` isn't the right way to do it. Because the value should be `$error` if the first argument isn't a boolean. As with the other boolean...

This should print an error message as noted above. See https://piazza.com/class/hgfxeb95g9z4vi?cid=77 for what goes wrong without an error message! (I got caught by this myself -- gave incorrect code on...