> So: do we have a concurrence here? dwheeler? I vote "Blank > comment-less line = end of expression".
Yes, I concur, "Blank comment-less line = end of expression". I redefined the indentation processor. > 1. By proper design of the SPLICE-at-the-start rule, we can also > define that SPLICE on a line, all by itself, followed by an expression > on the **same** indent, will mean just that expression. Thus, we gain > one more way to separate sub-expressions without using completely > blank lines. Good point. > Of course, by proper design of the SPLICE-inline rule (which would > subsume the SPLICE-at-the-end rule in the absence of that rule) we > have a different method of saying "I already typed the entire > expression" on the REPL. viz. instead of ENTER ENTER you type in > SPLICE ENTER. So we can actually decide "Blank commentless line = > does NOT end expression", since we now have a method to type in > one-line expressions and to finish multiline expressions at the REPL. > Err. What did I vote again? Ah, the danger of looking at both sides - you can convince yourself to vote both ways. :-). That's a fair argument, too. I think that at the interactive prompt, minimizing keystrokes is useful. ENTER ENTER is the shorter sequence, so let's make that execute-now. In code, including one character (like ; or SPLICE) to mean "intentionally empty line" seems plausible. The big risk is that someone will insert a truly empty line in the middle of an expression. If we warn every time an expression begins with space/tab, the risk goes down. So let's try it this way (as it already is), and use experimentation to see if that's enough. --- 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
