Some makefile.ss omissions

Bug #176682 reported by Derick Eddington on 2007-12-16
2
Affects Status Importance Assigned to Milestone
Ikarus Scheme
Medium
Abdulaziz Ghuloum
r6rs-libraries
Undecided
Unassigned

Bug Description

I made a makefile.ss checker (in my derick-ikarus-misc branch), and it discovered that:

makefile is missing identifiers:
 i/o-error-position
makefile identifiers not properly classified:
 eof-object?
  should be in: (psyntax scheme-report-environment-5) -> se
 null?
  should be in: (psyntax scheme-report-environment-5) -> se
 =>
  should be in: (psyntax scheme-report-environment-5) -> se
 else
  should be in: (psyntax scheme-report-environment-5) -> se
 ...
  should be in: (psyntax scheme-report-environment-5) -> se
 _
  should be in: (psyntax scheme-report-environment-5) -> se

leppie (leppie) wrote :

These are missing in psyntax too.

leppie (leppie) wrote :

&implementation should &implementation-violation.

Actually, it should be &implementation-restriction.

Abdulaziz Ghuloum (aghuloum) wrote :

Thanks. All were added in revision 1257, except for _ which does not belong to the scheme-environment.
See http://lists.r6rs.org/pipermail/r6rs-discuss/2007-September/003315.html for details.

Changed in ikarus:
assignee: nobody → aghuloum
importance: Undecided → Medium
status: New → Fix Committed
leppie (leppie) wrote :

Err, yes, thanks, was following the pattern :)

leppie (leppie) wrote :

I just spotted this in the spec, right at end of R6RS library spec, R5RS section.

"... The variable bindings
have as values the procedures of the same names described
in this report, and the keyword bindings, including
=>, ..., else, and are the same as those described in this
report."

So _ should be in the scheme-environment.

Abdulaziz Ghuloum (aghuloum) wrote :

The message linked-to above from Mike Sperber says that _ should not be included. So?

leppie (leppie) wrote :

I think I mis-pasted.

"... including =>, ..., else, and _ are ..."

Maybe the fix didn't get into the final version.

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:
http://www.cs.indiana.edu/~aghuloum/ikarus/ikarus-0.0.3-rc1.tar.gz
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