Am 19.11.2013 05:38, schrieb David A. Wheeler:
>> Am 18.11.2013 15:25, schrieb David A. Wheeler:
>>> On Mon, 18 Nov 2013 13:23:32 +0100, "Jörg F. Wittenberger"
>>>     <joerg.wittenber...@softeyes.net> wrote:
>>>
>>>> In a first attempt to feed the source to some other Scheme I went ahead
>>>> and sent it to the rscheme compiler.
>>>>
>>>> Doesn't work.  It has the same problem as Guile: it will refuse to read
>>>> certain #sharp syntax.
> Okay, the source code no longer has "#:".
>
> The result is extremely magical guile code, to work around some wonkiness in
> old versions of guile, but the magic is explained in comments.
>

Great if this works in guile, rscheme reads it too.  I'll be able to 
make progress.

However I have a problem with another change: while all the Scheme's I 
know process nested cond-expand forms I recall that srfi-0 explicit does 
not requites this to be the case and suggest to avoid such use.

Should be have these nested cond-expand's?

Also: often different Scheme's can share different code parts. Enforcing 
a single cond-expand with nested cond-expands is not only against 
srfi-10; I can foresee how this will complicate the code and require 
quite some repetition and confusing logic in those conditions the 
cond-expand's dispatch on.  Let alone that alternatives, which belong 
logically together are spread around in the file.  That's a nightmare to 
maintain.  Hence: I'd prefer to cluster all cond-expands at the 
beginning, but have one cond-expand per dispatch reason.

Comments?

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

Reply via email to