Alan Manuel Gloria: > Heya, it seems *> is going to be a bit of a bother... > > It's fine to detect <* in readblock-internal, then eat up horiz > whitespace and then call as a subroutine the upper-level > sugar-start-expr repeatedly until we somehow get to a *>. > > However, when readblock-internal detects *> while reading a head, it > needs to somehow signal the next higher readblock-internal in the call > chain and return to that (since *> is two characters, we can't unread > them both). > > Hmmmmm..... > > Any ideas? I have an idea, but I feel it's kinda ugly, so I'll > solicit some more ideas here before I show my own ^^
I think we should re-implement the indentation processor, regardless of <* ... *> or not. We inherited it from a much older SRFI, and it's gotten clunky. That *might* make it easier. Worse comes to worse, we can always use the unique-cons-tag trick. --- 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
