Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Christopher Reimer <christopher_reimer@icloud.com>
Newsgroups: comp.lang.python
Subject: Re: for / while else doesn't make sense
Date: Fri, 20 May 2016 20:47:27 -0700
Lines: 59
Message-ID: <mailman.68.1463802450.27390.python-list@python.org>
References: <CAHJ7fxhOeKFbu3=Jso=wgpBnH9Opr_J_6SHLDO+KtAqVFeGHnA@mail.gmail.com> <mailman.36.1463676220.27390.python-list@python.org> <dq71srF3j00U1@mid.individual.net> <573EC62F.4090401@lucidity.plus.com> <CAKJDb-Nj=Wr2=3ZL3n=xRCiCa6qVmyRX1P47Wvvy7EAw1izjLQ@mail.gmail.com> <d95ba62e-0acb-d0df-8eca-7b748d4730bb@icloud.com> <mailman.57.1463775663.27390.python-list@python.org> <573f9322$0$1616$c3e8da3$5496439d@news.astraweb.com> <44ec67e8-0c6e-54d9-c2fc-a4d9b78efb3d@icloud.com> <CAPTjJmrt1rYwZu-8mGsZf1-NeycF=iTGmAY8W9fSdJMB-7LWLw@mail.gmail.com> <1198e259-0bbb-f18a-e8d1-114bc84bf24c@icloud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
In-reply-to: <CAPTjJmrt1rYwZu-8mGsZf1-NeycF=iTGmAY8W9fSdJMB-7LWLw@mail.gmail.com>
Precedence: list
Xref: csiph.com comp.lang.python:108889

On 5/20/2016 7:31 PM, Chris Angelico wrote:

> On Sat, May 21, 2016 at 11:23 AM, Christopher Reimer
> <christopher_reimer@icloud.com> wrote:
>> On 5/20/2016 3:43 PM, Steven D'Aprano wrote:
>>
>>> But the idea that you should avoid a Python feature while programming in
>>> Python because Javascript doesn't have it, or Ruby, or C, is surely the
>>> height of muddleheaded thinking. You're not programming Javascript, Ruby
>>> or
>>> C, you're programming in Python. The whole point of picking one language
>>> over another is to get access to the tools and features that language
>>> offers. Otherwise you're just wasting your time.
>>
>> For many years I have resisted specializing in a programming language, as I
>> can easily write any program in pseudo code and figure out the syntax for a
>> particular language. Now it does help that most languages have derived from
>> C and share a common feature set (i.e., string, integer, float, if/else,
>> while, for, etc.). From my perspective, tacking on an else block to the end
>> of a for or while loop looks like a bug or a not very well thought out
>> feature. If I was translating a Python program with for/else or while/else
>> statements into a different language, those statements will have to be
>> rewritten anyway.
> That's fine, as long as you (a) restrict your programming languages to
> those derived from C, and (b) restrict your programming style to the
> common subset of them all. Trouble is, that "common subset" is
> actually pretty small. Strings behave very differently in C and high
> level languages, and for loops are *very* different in different
> languages. So you'd be throwing out a large amount of expressiveness,
> plus you're completely unable to use languages built on some other
> model (eg LISP, or DeScribe Macro Language, or APL).

I don't have a problem with (a) because the majority of the programming 
languages I've been exposed to have derived from the C language. No 
offense to the LISPers, but LISP is a historical curiosity that I might 
blow the dust off and take a look at someday. I'll probably learn 
assembly language before I ever look at LISP. :)

But I disagree with (b) on restricting myself to a common subset of ALL 
the programming languages. Pseudo code allows me to describe a program 
in very general details. Implementing a program in a programming 
language requires getting into very specific details. Of course, there 
are major and minor differences from language to language. If an oddball 
feature gets the job done, I'll use that. Or maybe not. If I'm uncertain 
about something, I'll keep going back and forth until I'm satisfied one 
way or another.

The else block tacked on to for and while loops in Python seems very 
oddball-ish to me. I've always strive to follow best practice whenever 
possible. The one book I've read -- and so far, the only book on that 
feature -- recommends not using it. Based on my previous experience, I 
don't disagree with that author's opinion. If I have a compelling reason 
to use it, I'll use it. Or I'll simplify it to use helper functions.

If I wanted to write portable code, I would have stayed with... Java. O_o

Thank you,

Chris R.