unbound identifiers should raise &undefined condition

Bug #178317 reported by leppie on 2007-12-23
Affects Status Importance Assigned to Milestone
Ikarus Scheme
Abdulaziz Ghuloum

Bug Description

As per summary.

leppie (leppie) wrote :

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


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.

Abdulaziz Ghuloum (aghuloum) wrote :

Okay. Done in revision 1284. Do you think the condition should have both &syntax and &undefined, or only &undefined?

Unhandled exception:
 Condition components:
   1. &who: dfkjhdksjfh
   2. &message: "unbound identifier"
   3. &undefined
   4. &source-information:
       file-name: "/tmp/foo.ss"
       character: 20

Changed in ikarus:
assignee: nobody → aghuloum
importance: Undecided → Low
status: New → Fix Committed

On Mon, 2007-12-24 at 00:54 +0000, Abdulaziz Ghuloum wrote:
> Okay. Done in revision 1284. Do you think the condition should have
> both &syntax and &undefined, or only &undefined?

My two cents is that it should only have &undefined, because the report
says &syntax "describes syntax violations" which implies the syntax
keyword is bound but was used incorrectly, whereas &undefined "describes
unbound identifiers in the program".

leppie (leppie) wrote :

I agree with Derick, but I am not sure that &who should imply '&what', so a &syntax for the form would be handy.

Abdulaziz Ghuloum (aghuloum) wrote :

This bug report is about to be closed as the fix comitted
previously will be incorporated in the next 0.0.3 release of
Ikarus Scheme, scheduled for January 31, 2008. A release
candidate tarball is available for download from:
Please do test it if you have the time and report any issues
you might encounter. Thank you very much for your support.
(Sorry for the duplicates; I'm updating every open bug.)

Changed in ikarus:
milestone: none → 0.0.3
Changed in ikarus:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers