Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!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.010 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'operator': 0.03; 'languages,': 0.04; 'assignment': 0.07; 'function,': 0.09; 'mess': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'confuse': 0.16; 'did.': 0.16; 'message-id:@4ax.com': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'skip:> 20': 0.16; 'subject:between': 0.16; 'subject:tasks': 0.16; 'url:home': 0.24; '(or': 0.24; 'header:X-Complaints-To:1': 0.27; 'function': 0.29; 'that.': 0.31; 'about.': 0.31; 'break;': 0.31; 'comparison': 0.31; 'equality': 0.31; 'pascal': 0.31; 'subject:the': 0.34; "i'd": 0.34; 'something': 0.35; "didn't": 0.36; 'charset:us-ascii': 0.36; 'subject:?': 0.36; 'level': 0.37; 'being': 0.38; 'to:addr:python-list': 0.38; 'rather': 0.38; 'that,': 0.38; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'even': 0.60; 'expression': 0.60; 'first': 0.61; 'term': 0.63; 'more': 0.64; 'chance': 0.65; 'statement,': 0.68; '2015': 0.84; 'balanced': 0.84; 'goto': 0.84; 'collective': 0.91; 'received:108': 0.93 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Dennis Lee Bieber Subject: Re: asyncio: What is the difference between tasks, futures, and coroutines? Date: Wed, 06 May 2015 09:11:15 -0400 Organization: IISS Elusive Unicorn References: <344fd8f6-75c1-4b7d-888d-c5c9d4498ec3@googlegroups.com> <878ud27waw.fsf@elektro.pacujo.net> <4ea2d5ac-8c19-4a53-9a09-fe6dbe4a52bd@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: adsl-108-68-176-228.dsl.klmzmi.sbcglobal.net X-Newsreader: Forte Agent 6.00/32.1186 X-No-Archive: YES X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ 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: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1430917883 news.xs4all.nl 2928 [2001:888:2000:d::a6]:39915 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:90052 On Tue, 5 May 2015 21:47:17 -0700 (PDT), Rustom Mody declaimed the following: >If the classic Pascal (or Fortran or Basic) sibling balanced abstractions of function-for-value >procedure-for-effect were more in the collective consciousness rather than C's >travesty of function, things might not have been so messy. > I suspect just the term "subprogram" (as in "function subprogram" and "subroutine subprogram") would confuse a lot of cubs these days... >C didn't start the mess of mixing procedure and function -- Lisp/Apl did. >Nor the confusion of = for assignment; Fortran did that. I don't think you can blame FORTRAN for that, given that it was one of the first of the higher level languages, and had no confusion internally... The comparison operator being .EQ. (and kin: .LT. .GT. .LE. .GE. .NE.); and with assignment as a statement, not an expression in its own right, no chance of even something like IF (X = Y .EQ. Z) GOTO 123 to be concerned about. Confusion over assignment vs equality I'd lay firmly on C if (x = y == z) break; -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/