Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.033 X-Spam-Evidence: '*H*': 0.93; '*S*': 0.00; 'agree,': 0.09; 'propagate': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; '"end"': 0.16; 'braces': 0.16; 'braces,': 0.16; 'brackets': 0.16; 'curly': 0.16; 'delimiters': 0.16; 'escapes': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'locally,': 0.16; 'marker': 0.16; 'massively': 0.16; 'merger': 0.16; 'nose': 0.16; 'retained': 0.16; 'rigid': 0.16; 'syntactic': 0.16; 'folks': 0.16; 'wrote:': 0.18; 'wed,': 0.18; 'trying': 0.19; "python's": 0.19; 'cc:addr:python.org': 0.22; 'issue,': 0.24; '(or': 0.24; 'cc:2**0': 0.24; 'pass': 0.26; 'header:In-Reply- To:1': 0.27; 'point': 0.28; 'am,': 0.29; 'message- id:@mail.gmail.com': 0.30; "i'm": 0.30; 'code': 0.31; 'that.': 0.31; 'indentation': 0.31; 'minor': 0.31; 'languages': 0.32; 'quite': 0.32; 'problem': 0.35; 'etc': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'google': 0.35; 'too': 0.37; 'issue': 0.38; 'pm,': 0.38; 'that,': 0.38; 'either': 0.39; 'space': 0.40; 'even': 0.60; 'skip:u 10': 0.60; 'new': 0.61; 'simple': 0.61; 'reply': 0.66; 'between': 0.67; 'debate': 0.68; 'url:tinyurl': 0.69; 'wish': 0.70; 'subject:This': 0.74; 'lack': 0.78; 'adopts': 0.84; 'cole': 0.84; 'flame': 0.84; 'forced': 0.84; 'adopt': 0.91; 'hate': 0.91; 'lazy': 0.91; 'to:none': 0.92; 'baby': 0.95 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=fXPQ3wPIoAvvBJR2C/YHlIsK6/TzQBRg5lfN6gHmNO0=; b=TAmNAnW1gwCBITRmaCEoMb/dsp4VqFuc9oE/lCetYtcY4MzGw6EDpaSX851Fk9P2KF L8Bk73EDX/yO+xLdPWCF4DbEUYCsPO1yagVkF8OJAo5o9Cg7sQahw/pjBCi+xVC9DC1Y t2BEqXkbYP/Jo9/JlIlKM3AC5zWuQfWCoKss3iP5QRb7d6csTDUhjnAWeAdlTK3tvN5s HFJODWIQZKQ5Fchz076HPquhFzZS8InCfINdGtQGb61RaSXJMTzXZkr+5PXq8apM5pYn c1sF8di5HczvdzkkcTRZSQKrbvEYhlhKuS9fGokvy8xzLBMu+yl3uzg7AnAkZ9o5UAs8 N8hA== MIME-Version: 1.0 X-Received: by 10.58.152.137 with SMTP id uy9mr4693117veb.54.1401832896421; Tue, 03 Jun 2014 15:01:36 -0700 (PDT) In-Reply-To: References: <34564700423508781.788278sturla.molden-gmail.com@news.gmane.org> Date: Wed, 4 Jun 2014 08:01:36 +1000 Subject: Re: OT: This Swift thing From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 39 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1401832898 news.xs4all.nl 2920 [2001:888:2000:d::a6]:50953 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:72556 On Wed, Jun 4, 2014 at 7:49 AM, Mark H Harris wrote: > On 6/3/14 3:43 PM, Sturla Molden wrote: >> >> Nicholas Cole wrote: > >> {snip} > >> Unfortunately they retained the curly brackets from JS... >> > > The curly braces come from C, and before that B and A/. > > (I think others used them too before that, but it escapes me now and I'm too > lazy to google it) > > ... but the point is that curly braces don't come from JS ! If a merger between JS and Python adopts braces, the braces came from JS. You look at a baby and say he has his father's nose (http://tinyurl.com/kqltth4 perhaps?), not that he has his great-grandmother's nose, even if it's the same nose. > I have been engaged in a minor flame debate (locally) over block delimiters > (or lack thereof) which I'm loosing. Locally, people hate python's > indentation block delimiting, and wish python would adopt curly braces. I do > not agree, of course; however, I am noticing when new languages come out > they either use END (as in Julia) or they propagate the curly braces > paradigm as in C. The issue locally is trying to pass code snippets around > the net informally is a problem with indentation. My reply is, well, don't > do that. For what I see as a freedom issue, folks want to format their white > space (style) their way and don't want to be forced into an indentation > paradigm that is rigid (or no so much!). I quite like braces, myself, but I'm happy with either model. But I don't like massively verbose "END" blocks, nor the syntactic salt of bash's case/esac, if/fi, etc (match the end marker to the beginning). Keep it simple and keep it unobtrusive. ChrisA