Comment 2 for bug 178317

I mean just trying to use some unbound identifier raises &syntax (via stx-error). Like:

some-undefined/unbound-id

This seems to be raised as (stx-error id "unbound identifier"). Most notably in the syntax-type procedure.

According to the spec, &undefined condition should be used for unbound identifiers.

More info: I am just setting up a little test library. Example:

(test 'hello => 'hello)
(test hello &> &syntax) ; should be &undefined
(test (hello) &> &syntax) ; should be &undefined
(test (car '1) &> &assertion)
(test (car) &> &syntax)

To test expected exceptions/behaviour/etc.