Issues:

1) I can't think of any other immediately useful ck-macros.

2) I don't see a need for direct support of dotted lists, and still less of circular lists.

3) Since the CK-machine is not exposed, I think it's not a good choice of prefixes. I'd go with "eager macros", since the salient point of these macros is that they eagerly evaluate their arguments. "Applicative macros" would work too, but I don't think it is as good. So both "composable macro" and "ck-macro" should be changed to "eager macro". A good prefix would be "em".

4) I would replace ck-expression with just the prefix, so "ck" or "em" as the case may be.

5) I don't think anonymous macros are necessary given ck-cut and ck-cute.

Other things:

6) For ck-macro-expander read ck-macro-transformer, to follow the pattern of sc-, rsc-, er-, ir-macro-transformer. Or alternatively eager-syntax-rules or em-syntax-rules.

7) The hyphen after the prefix should be omitted for readability and clarity if the next character is symbolic. Thus ck+, ck-, ck<=, etc. I'm not sure about ck-0 vs ck0, etc. Being systematic is not essential here (cf. SRFI 1 list=, etc.)

8) ck-and and ck-or templates don't have an ellipsis.

9) I think ck-fact should be replaced by ck-perm or ck-permutation.

John Cowan http://vrici.lojban.org/~cowan xxxxxx@ccil.org

LEAR: Dost thou call me fool, boy?

FOOL: All thy other titles thou hast given away:

That thou wast born with.