Alan Manuel Gloria wrote on Fri, 27 Jul: > Well I was only envisioning a stable spec we can code to on July 31, > but if you think it's possible to get an actual 0.3 release > implementation, that's fine.
I think we can. I envision our "Solution" page as the "stable spec". It'd be good to have a more formal and rigorous specification, but we can work on that over time. > Although unfortunately I might be a tad busy this weekend, and I still > have to actually fix the comments implementation. RL concerns. Also > a little case of colds. Sorry to hear about the cold, hope you feel better. I notice that since you said that, you submitted commit 5fa425f68af901bc0de55dd89f541099d7365dd0 on July 28, to "Handle multiline comments and other #-foolery." And of course, earlier commit 80da4a477e531e6995f4e06b84aade2efac419a4 fixed the bug where an open paren was immediately followed by a semicolon. So at this point, I don't know of anything in the comments implementation that needs fixing; all seems to be working properly. Anything else? --- 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
