> How's the end of July (July 31) sound? What I really need are the > specs I can code to, not necessarily a complete reader - I can help > implement a complete reader, but I really want a stable spec I can > code to and implement.
Agreeing on a spec by then seems very doable, especially since there's really only one key issue that needs discussion. Indeed, since we have a plausible backoff plan, we can guarantee to have *a* spec by then :-). I think we need to collect the various semantic options and symbol options in one place, based on the mailing stream, ID their pros and cons, and then select. You've done some nice summaries in the past, want to try at that? If it's complicated to do on the mailing list, we could open and co-edit a Wiki page to capture the options. You have read/write privs on our Wiki. > Well, here's an example of code that I've started to write, but which > really really needs SPLICE. Thanks for the example; it's important that whatever notation we agree on be useful for "real life". I suggest we it use it as one of the test cases for the various semantics. --- 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
