Here are highlights of the changes to SRFI-105:

* Mandate equal? comparison for simple curly-infix lists, e.g., to handle ",op" as an operator See http://srfi.schemers.org/srfi-105/mail-archive/msg00018.html http://srfi.schemers.org/srfi-105/mail-archive/msg00027.html
*    More examples, make clear in the abstract that the users are ANYONE who wants infix, both those less familiar and those very familiar with Scheme. http://srfi.schemers.org/srfi-105/mail-archive/msg00014.html http://srfi.schemers.org/srfi-105/mail-archive/msg00015.html
*   Mandate returning nfx, and drop transform-mixed-infix. http://srfi.schemers.org/srfi-105/mail-archive/msg00018.html
*    Make it clear that application authors can override/define "nfx".
*    Handle f(x).  I've embedded neoteric-expressions inside curly-infix. http://srfi.schemers.org/srfi-105/mail-archive/msg00000.html http://srfi.schemers.org/srfi-105/mail-archive/msg00001.html  This means that {-(x) / y} is allowed, for example.
*    Drop enable-..., and add marker such as #!srfi-105 or #!c-expr http://srfi.schemers.org/srfi-105/mail-archive/msg00027.html  A lengthy rationale was added to discuss this.

--- David A. Wheeler