Alan Manuel Gloria:
> Okay, fine, I don't like it (inconsistency here concerns me), but I
> won't oppose it. Will not support, will not oppose.
>
> Here's another question. I assume that { foo(bar(nitz)) } is (foo
> (bar nitz)), i.e. n-expressionism is recursive within curlies.
Yes.
> How will we implement the reader? The current implementation is much
> simpler as it is simply a hook that gets triggered on {, but with
> n-expressions inside curlies, we'll have to show a reference
> implementation that replaces 'read.
I believe it's pretty easy *if* the reader's delimiters include {}. In fact,
it may simplify the implementation. In our implementation, I think it means
that my-read-delimited-list will *always* call neoteric-read-nocomment. Let's
prototype this in stages, but it may mean that we drop the reader parameter
entirely throughout all the code, which would actually simplify everything.
In this modified curly-expression-only reader, the topmost level probably
shouldn't allow neoteric-expressions, e.g., we shouldn't allow:
{a + b}(7)
We could code it either way, but I think that people are thinking that "{"
enables neoteric-reading in this case, so the final "}" should end it. I
suspect most people won't notice the difference, and you could always use this
if you wanted it:
{ {a + b}(7) }
or, use sweet-expressions, where it *would* work.
I don't intend to change sweet-expressions for this change. In
sweet-expressions, I still intend to say that you can say f(x) anywhere. The
only effect is that in SRFI-105-only systems, f(x) is enabled *inside* but not
*outside* curly-infix.
--- David A. Wheeler
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Readable-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/readable-discuss
