[bitc-dev] On whitespace sensitivity (was Re: Opinions wanted: Infix shift operators)
william.leslie.ttg at gmail.com
Mon Aug 9 01:38:17 PDT 2010
On 9 August 2010 17:18, Nathaniel W Filardo <nwf at cs.jhu.edu> wrote:
> On Mon, Aug 09, 2010 at 03:07:57PM +1000, William Leslie wrote:
>> If you need to use that you probably have other problems. Line
>> continuation is implicit inside parenthesis, braces and brackets,
>> which is the only place you'd ever want them.
> I want to write
> print "some overly long description that %s went wrong because %d" %
> (something, someotherthing)
> and no,
> print "some overly long description that %s went wrong because %d" % (
> something, someotherthing)
> is not acceptable for obvious reasons, nor is
It's not pretty, but it's readable, which is what counts. I admit I
use this idiom a lot, when I should be moving to several expressions
> print ("some overly long description that %s went wrong because %d" %
> (something, someotherthing))
> because I have to remember to write the outer parens.
0. "I have to remember the semicolon"
1. "I have to remember under what conditions ecmascript does semicolon
2. "I have to remember which keywords in t-sql or ruby take precedence
over this one, or add delimiters if I ever change the expression that
Not having lines as the primary statement delimiter means you
frequently need to take in more non-linear context to understand
program flow. And as a minimum, statements on one line make it easier
to understand syntax errors.
More information about the bitc-dev