Did I say "next week"? I should rather do something else, but I can't fight myself. :-/
Bad news this time. Am 22.11.2013 14:59, schrieb David A. Wheeler: > On Fri, 22 Nov 2013 10:26:58 +0100, "Jörg F. Wittenberger" > <joerg.wittenber...@softeyes.net> wrote: > >>> Why all the redefines from "body" to "read-body"? >>> We normally use the same name as per the grammar. >> RScheme idiosyncratic: `body` is already a bound elsewhere within some >> code required com compile this code. >> Hence RScheme complains about the "semantic error" and that redefinition >> would break things. >> >> The only reasonable way I saw was to change the name to avoid the conflict. >> >> However by re-considering the case now I understand that the desire to >> keep `body` there literally to match the grammar. In that case we >> should macro-define body into read-body for RScheme only. > If Rscheme will accept that without complaint, that'd be very nice. > Otherwise, I'm happy to rename definitions to make it work... I just > want to minimize it, and document why there's a variance when it happens. I'd now rather take back my suggestion to macro-define around: while it would work for the call site, I have no (good) idea how to change the definition. Furthermore bad news regarding the idea to move those cond-expand's into the read-able-module-contents. The problem is not cond-expand, but rscheme accepts define-macro only at top level. The attached patch has a strange name in a way, considering that it contains much more than this. However it also fixes a bug in n-expr-or-scomment. David, could you merge this into the git repo? The next thing I'd try to get around would be making those settings port specific. But I'd rather like to keep those diffs size down. Best Regards /Jörg ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
