Beni Cherniavsky-Paskin: > foo > ! ! bar > ! baz quux > currently (I'm running git head on guile 1.8.7) parses as 2 separate > expressions: > (foo bar) > (baz quux) > which sounds like a bug to me for 2 reasons:- baz's indentation != foo's > indentation- iff baz starts a new expression, it should have triggered > the "indented-compatibility" mode
It's actually not clear what we *should* do in this case, so let's talk about that. This code isn't formatted the way it should be; the partial-outdent of the third line shouldn't happen at all. So.. then what? To be honest, it might be best to report an error, consume the rest of the lines until we get a fresh start (e.g., blank line), and start over. It seems unlikely that indented-compatibility mode was intended in this case, since we started with correct indentation. Thoughts? What would people suggest? --- 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
