Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.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.008 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'python.': 0.02; 'subsequent': 0.05; '*is*': 0.09; 'english,': 0.09; 'formatting': 0.09; 'lines:': 0.09; 'subject:design': 0.09; 'sure,': 0.09; 'throws': 0.09; 'width': 0.09; 'python': 0.11; '"create': 0.16; '"insert': 0.16; 'dict': 0.16; 'formatting.': 0.16; 'frame,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'materially': 0.16; 'paragraphs,': 0.16; 'portable': 0.16; 'reedy': 0.16; 'subject:Language': 0.16; 'sunny': 0.16; 'uncommon': 0.16; 'eager': 0.16; 'sat,': 0.16; 'wrote:': 0.18; 'replace': 0.24; 'text,': 0.24; 'looks': 0.24; 'nearly': 0.26; 'primary': 0.26; 'values': 0.27; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; "doesn't": 0.30; 'document.': 0.30; 'message- id:@mail.gmail.com': 0.30; 'code': 0.31; 'usually': 0.31; 'indentation': 0.31; 'sep': 0.31; 'universal': 0.31; 'figure': 0.32; "we're": 0.32; 'quite': 0.32; 'table': 0.34; 'there,': 0.34; 'could': 0.34; 'but': 0.35; 'received:google.com': 0.35; '14,': 0.36; 'like,': 0.36; 'possible': 0.36; 'changing': 0.37; 'easily': 0.37; 'convention': 0.38; 'to:addr:python-list': 0.38; 'that,': 0.38; 'structure': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'eye': 0.61; 'mentioned': 0.61; 'entire': 0.61; 'took': 0.61; 'simple': 0.61; 'first': 0.61; 'making': 0.63; 'july': 0.63; 'more': 0.64; 'talking': 0.65; 'hints': 0.68; 'fact,': 0.69; '(word': 0.84; 'divide': 0.84; 'ear': 0.84; 'evening': 0.84; 'laid': 0.84; 'near,': 0.84; 'sky': 0.84; 'same,': 0.91; 'write:': 0.91; '2013': 0.98 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:to :content-type; bh=3rGrpf9OQGjYinnmDR9+RateGDWCqcZeF6mLJ2AaGzs=; b=UVicAG8V7c17GxSKk1yI994KZ7MgBpwLs0S8eTuFTLl1672MbNWXF9py3q2/RtHUbG FcUKGXxZ7qosUZGlFREzeYpLcGIz5jbX5pzsxOQGCMjVWHUnHq/N64pIuK8VQmQx++1S EmSrYUghz7W0Bc+uPfj5G2oa2nx1K+JYAp1IGfDgMA0f63fww5K9DC3MDSF9XdSD2xbJ Q1amyeBbZf1Ekpksp3gqcDMdNTaCvfSKidhZLXD2WafUBO8z5yactnl3snss97Ha1jM9 Bmbwl0rRpZX5gPo7gBGPZ9iaFXynHIy6v/Bgsa3DWTDPvfXjrT2K08jzDspVslly5cg1 yMow== MIME-Version: 1.0 X-Received: by 10.59.8.232 with SMTP id dn8mr14342737ved.8.1379116656710; Fri, 13 Sep 2013 16:57:36 -0700 (PDT) In-Reply-To: References: <522eb795$0$29999$c3e8da3$5496439d@news.astraweb.com> <5232e562$0$29988$c3e8da3$5496439d@news.astraweb.com> Date: Sat, 14 Sep 2013 09:57:36 +1000 Subject: Re: Language design From: Chris Angelico To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 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: 45 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1379116659 news.xs4all.nl 15911 [2001:888:2000:d::a6]:49079 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:54145 On Sat, Sep 14, 2013 at 5:32 AM, Terry Reedy wrote: > Poetry, including that in English, often *is* concerned with formatting. > Code is more like poetry than prose. > > >> You can take this >> paragraph of text, unwrap it, and then reflow it to any width you >> like, without materially changing my points. > > > But you cannot do that with poetry! Evangelical vicar in want of a portable second-hand font. Would dispose, for the same, of a portrait, in frame, of the Bishop-elect of Vermont. I think you could quite easily reconstruct the formatting of that, based on its internal structure. Even in poetry, English doesn't depend on its formatting nearly as much as Python does; and even there, it's line breaks, not indentation - so we're talking more like REXX than Python. In fact, it's not uncommon for poetry to be laid out on a single line with slashes to divide lines: A boat beneath a sunny sky / Lingering onward dreamily / In an evening of July / Children three that nestle near, / Eager eye and willing ear / Pleased a simple tale to hear... in the same way that I might write: call sqlexec "connect to words"; call sqlexec "create table dict (word varchar(20) not null)"; call sqlexec "insert into dict values ('spam')"; call sqlexec "insert into dict values ('ham')" To be sure, it looks nicer laid out with line breaks; but it's possible to replace them with other markers. And indentation still is completely insignificant. The only case I can think of in English of indentation mattering is the one you mentioned of first line of subsequent paragraphs, not by any means a universal convention and definitely not the primary structure of the entire document. Making line breaks significant usually throws people. It took my players a lot of time and hints to figure this out: http://rosuav.com/1/?id=969 ChrisA