On 9 August 2010 17:18, Nathaniel W Filardo <n...@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
and variables.
> print ("some overly long description that %s went wrong because %d" %
> (something, someotherthing))
> because I have to remember to write the outer parens.
Compare with:
0. "I have to remember the semicolon"
1. "I have to remember under what conditions ecmascript does semicolon
insertion"
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
follows"
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.
--
William Leslie
_______________________________________________
bitc-dev mailing list
bitc-dev@coyotos.org
http://www.coyotos.org/mailman/listinfo/bitc-dev
