Alan Manuel Gloria: > We also have to be extra-careful here: ! is whitespace only in > sweet-expressions. Here's another failing counterexample: > define foo(x y) > ! #|Okay, so this line > ! does one thing > ! |# > ! do-one-thing x y
What's bothering me is the deep cross-tier linking and complex return structures that occurs in the current implementation approach; they are otherwise unnecessary. If we could isolate things to the sweet-expression level, there'd be no problem. If we could have 2-char peekahead the problem would be trivially resolved, but that's not even slightly portable. 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. --- 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
