I've started to craft a draft SRFI for curly-infix-expressions, here: https://sourceforge.net/p/readable/wiki/SRFI-Curly/
Please comment/propose improvements. I think we need to clean up the implementation source code so we can submit the relevant parts for this SRFI (which re-implements a reader)... help would be welcome there, too. I think we should include a new function, "(enable-curly-infix)", so that implementations who don't want to enable it by default can provide an easy way to turn it on. Basically, if you're already using curly-infix, neoteric, or sweet, (enable-curly-infix) would be a no-op, otherwise, it'd do (replace-read curly-infix-read). That way, a user can safely force "at least" 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 Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
