> > So I propose the following semantic changes:
> > * Curly-infix: If the length is 0, return () not (nfx).
> > * Neoteric-expressions: Given e{...}, if the curly expression {} returns
> > (), map it to (e).
Alan Manuel Gloria replied:
> Seems OK by me.
Okay, I've implemented it in the development branch the "main" kernel.scm
(though not yet in the srfi simplified implementation).
Let's try it out!
If it seems reasonable, we'll need to modify the spec, though this one's easy.
I've added text to [Solution] to note that this might become the case. It'd be
version 0.5 at that point.
I think we also need to nail down the semantics for improper lists in {...}
before we update to spec version 0.5.
--- 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
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss
