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

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

This page is part of the web mail archives of SRFI 108 from before July 7th, 2015. The new archives for SRFI 108 contain all messages, not just those from before July 7th, 2015.

I updated http://per.bothner.com/tmp/srfi-108/srfi-108.html
to hopefully satisfy your comments below.

On 03/26/2013 11:52 PM, John Cowan wrote:
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.


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".

Fixed (two places).
	--Per Bothner
per@xxxxxxxxxxx   http://per.bothner.com/