I said: > PROPOSAL: Change the semantics of #|...|# for the sweet-reader to: "All > whitespace and ;-comments after multi-character comments are consumed; the > datum is considered to begin where the comment began. This is because a > #|...|# comment is read recursively by the neoteric reader."
This is probably more easily said by reversing its order: PROPOSAL: All datums beginning with "#" are read by the neoteric reader. Thus, all whitespace and ;-comments after #|...|# comments are consumed, and the datum is considered to begin where the comment began. This is *already* the rule for "#;", it's just generalized, and is WAY easier to implement. I understand if this proposal delays 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
