John Cowan: > I think that that should work. See, if you think of \f as another kind > of newline, then it's perfectly reasonable: the next page starts with > a comment. So how about just treating \f (and \v) as \n, at least when > outside a comment? That way, something like "foo\n\f\;comment\n" does > what I would expect: the blank line is between \n and \f.
We could certainly do that, and the productions would become slightly simpler. But that would be extremely permissive. That would mean that (for example) any line would "terminate" with FF/VT, including ;-only lines. E.G.: ; Hi \fbar bar ==> (bar bar) Do we really want that? I suspect very few tools are prepared to deal with FF/VT as a line terminator, certainly vim doesn't see it that way. And I fear that would create unnecessary surprises and allow confusing code. The current ruleset bounds FF and VT rather tightly, so that they can only be used on "lines by themselves" to divide code; that's the only use I've see of them. --- David A. Wheeler ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss