I said: > > Here's an alternative: Couldn't the sweet-expression reader peek for an > > initial "#", and if it's there, re-implement *just* # processing? Then it > > could include support for the "comment-tag" for #|...|#, but it'd be > > isolated to the sweet-expression level. That'd isolate it to just the > > sweet-expression processing. Then neoteric-read would only encounter > > #|...|# inside a list, where it could recurse without problems.
Alan Manuel Gloria: > This sounds like a better idea. The sweet-expression reader already > does something different when it encounters # at the top-level. Okay, that's now implemented in the devel branch. Looks like it works well. So let's leave #|...|# semantics as they are. We'll need to do more code simplifications, since that is no longer needed in the lower tiers, and the sweet-expression implementation is still clunky, but that can be done in stages. --- 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
