Alan Manuel Gloria: > 4. I can't accept #4 because I'm not assured that it is easy to > implement given a one-character lookahead implementation (Scheme). I > think that it is a significant implementation burden, in order to > support what I consider to be minor advantages.
I just posted an updated reader with that implementation, it turned out to be really easy to implement with unread-char. While unread-char isn't part of R5RS, it's available in at least two Schemes, and we could create little portability layer to implement unread-char for other Schemes. So since it's easy to implement, can you accept #4 (period + space or tab as indentation)? --- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/readable-discuss
