[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Bug report: low-level macros vs. variables in csi
From: |
Felix Winkelmann |
Subject: |
Re: [Chicken-users] Bug report: low-level macros vs. variables in csi |
Date: |
Sat, 15 Mar 2008 17:28:02 +0100 (CET) |
From: John Cowan <address@hidden>
Subject: [Chicken-users] Bug report: low-level macros vs. variables in csi
Date: Thu, 13 Mar 2008 12:05:08 -0400
>
> So in effect the names "cond" and "yammer" have two definitions,
> one in the car position of a non-atomic form, and the other
> everywhere else. This is contrary to the behavior of other Schemes,
> csi when a syntax-expander egg is loaded (tested under syntax-case,
> syntactic-closures, and riaxpander), and csc.
>
> Proposed course of action: have the interpreter check whether an
> identifier is the name of a macro and signal an error rather than using
> any existing definition.
No, bad idea. The current behaviour is IMHO acceptable considering the
use of low-level macros. More consistent and cleaner semantics can be
achieved with a more powerful macro expander.
cheers,
felix