Email list hosting service & mailing list manager

SRFI 136 draft 3 (<type-name> ...) macro-expansion, etc. Sudarshan S Chawathe (03 Nov 2016 00:13 UTC)
Re: SRFI 136 draft 3 (<type-name> ...) macro-expansion, etc. Marc Nieper-Wißkirchen (04 Nov 2016 21:27 UTC)

SRFI 136 draft 3 (<type-name> ...) macro-expansion, etc. Sudarshan S Chawathe 03 Nov 2016 00:12 UTC

Here are some comments based on my reading of Draft #3 of SRFI-136.  All
except the first are minor, and the first may just be confusion at my
end.

  * I'm having difficulty understanding the motivation for the
    description of the macro use that appears just before the
    Procedures section of the document:

      (<type-name (<keyword> <datum> ...))

		I looked in the tests included in the sample implementation hoping
    to find an example that may help me, but couldn't. (I may have
    missed it.)  This may well be a problem at only my end, but perhaps
    a brief mention of the motivation at this point would be useful to
    others as well.

  * In the Procedures section, I believe the third procedure's
    specification should read

      (record-type-descriptor record)

    instead of

      (record-type descriptor record)

  * In the description of make-record-type-descriptor, is the use of
    quotes (') before <type name> and (<field spec> ...) signifcant?

  * (minor) In the Syntax section, I believe the <macro use> rule
 	   extends Section 7.1.3 of R7RS, which may be worth noting (or
 	   not).

  * (nit) Second paragraph below the grammar in the Syntax section:
    Should "define a keyword" read "defines a keyword (for consistency
    with the other items)?  (I only mention this ridiculously minor item
    because the rest of the document is very consistent.)

Regards,

-chaw