I have a draft R7RS post ready to go. But now that I've read a lot of the R7 mail archive and website, I don't think the post will work as-is. I suggest a shift in direction instead.
I think we ought to propose a SRFI for just curly-infix, FIRST, and then invite the WG to contribute if they'd like (with a pointer to the SRFI). At which point the WG email is just an FYI. After reading the R7RS discussions, I think proposing to add something in R7RS that is not yet implemented in many Schemes, especially an infix notation, is highly unlikely to work. Especially at their current stage. Currently the R7RS group is working on "Small" Scheme, and they may have completed their last round. They've even voted to remove caddr and friends, which are universal and have been in Scheme since the beginning I believe. (How it helps portability by *removing* standard functions from R5RS is a mystery to me; the set of functions that work across R4, R5, R6, and draft R7 may be approaching the empty set.) I think we'd have better luck getting a SRFI through (with an announcement elsewhere), then getting code into some implementations to implement the SRFI. *Then* we'll have more luck, methinks. We might manage to hit a window for R7RS "Large", where they might be more receptive too. Thoughts? --- 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
