Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think!snorkelwacker!bloom-beacon!ZURICH.AI.MIT.EDU!cph
From: cph@ZURICH.AI.MIT.EDU (Chris Hanson)
Newsgroups: comp.lang.scheme
Subject: Bug in MIT-Scheme
Message-ID: <9003262207.AA11761@life.ai.mit.edu>
Date: 26 Mar 90 22:07:17 GMT
References: <1254@tub.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 22


   Date: 22 Mar 90 09:50:24 GMT
   From: Oliver Laumann <mcsun!unido!tub!net@uunet.uu.net>

   Now let me turn your attention to a real bug in C-Scheme:

   The C-Scheme reader refuses to parse numeric constants like #o-10
   (i.e. a radix followed by a sign followed by digits).  On the other
   hand, it happily accepts something like -#o10.  This must be a bug,
   since the standard clearly says that the radix, like the exactness
   specification, is a prefix (see page 37 of the P1178/D3 or page 32
   of the R^3.99RS), so #o-10 is the correct form, while -#o10 should
   be parsed into two objects, the symbol "-" followed by #o10.

If you had read a little more carefully you would have found that the
syntax changed between R3RS and R3.99RS.  MIT Scheme 6.1.2 and 7.0
conform to R3RS, accepting `-#o10' and refusing `#o-10'.  The current
version of MIT Scheme, sometime to be released as version 7.1,
conforms to R3.99RS and the standard.

Given that neither the standard nor R4RS is yet finished, I think it's
fair to say that the current MIT Scheme conforms to current standards.