[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: srfi-108 (named quasi-literal constructors) candidate



Per Bothner scripsit:

> http://per.bothner.com/tmp/srfi-108/srfi-108.html

In the abstract, "The reader translates &tag{...} to a list
$(construct$:tag ...), where construct$:tag is normally bound to a
predefined macro" has $( for ($ and omits $ after "where ".

"two different purposes": Adopt SRFI 109 language.

In "Translating enclosed expressions", shift the current language to
the top of the section and the former language (involving $unquote$)
to the bottom, for the sake of clarity.

Migrate the discussion of delimiter options, which is mostly of
historical interest, to the bottom of the SRFI.  Note that R7RS now
allows identifiers to begin with @, and disambiguates using ,@foo =
(splicing-unquote foo) versus , @foo (unquote @foo).

Starting an identifier with "&" is not at all rare in R6RS, where it is
conventional in the names of record types.  However, the rest of that
paragraph is valid.

For "specifiction" read "specification".

-- 
MEET US AT POINT ORANGE AT MIDNIGHT BRING YOUR DUCK OR PREPARE TO FACE WUGGUMS
John Cowan      cowan@xxxxxxxx      http://www.ccil.org/~cowan