[gambit-list] Conflict bewteen #<<c-declare-end and syntax-case?

Marc Feeley feeley at iro.umontreal.ca
Sat Mar 24 22:19:52 EDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8-Feb-07, at 1:31 PM, Raffael Cavallaro wrote:

>
> On Feb 7, 2007, at 8:06 PM, Marc Feeley wrote:
>
>> It's probably easy to fix for the implementors of syntax-case  
>> (Dybvig et al), but I shudder at the thought of figuring out which  
>> of the over 40 usages of 'quote in syntax-case.scm has to be made  
>> conditional on the object being quoted (the quote should be  
>> dropped for strings, numbers, booleans, and characters).
>
> Given that you can't fix syntax-case.scm, would it be possible to  
> modify c-declare, etc. so that they take both strings and quoted  
> strings?
>
> regards,
>
> Ralph
>
> Raffael Cavallaro, Ph.D.
> raffaelcavallaro at mac.com

I finally figured out how to change syntax-case.scm to avoid quoting  
self-evaluating constants.  I uploaded a new version here:

   http://www.iro.umontreal.ca/~gambit/syntax-case.scm

It will be included in the next release of Gambit.  This version of  
syntax-case will thus leave mostly as-is calls to Gambit specific  
forms such as "namespace", "declare", "c-declare", etc so that they  
are properly handled by Gambit.  It is still not a perfect  
integration but probably good enough (for example the arguments of  
"namespace", "declare", etc will be expanded if they happen to be  
syntactic forms defined with syntax-case).

Marc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFGBdxI//V9Zc2T/v4RAosUAJ0RhUWkTkL7tyV13S0o+735mGbrXQCgopHF
3yaflEi7uwY1Kn0w2gn4WkU=
=zfBU
-----END PGP SIGNATURE-----



More information about the Gambit-list mailing list