Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77355
Return-Path: <leight@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 48384 invoked from network); 19 Sep 2014 23:20:25 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Sep 2014 23:20:25 -0000
Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
X-PHP-List-Original-Sender: leight@gmail.com
X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com  
Received: from [209.85.212.171] ([209.85.212.171:39725] helo=mail-wi0-f171.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 26/B5-13213-83ABC145 for <internals@lists.php.net>; Fri, 19 Sep 2014 19:20:25 -0400
Received: by mail-wi0-f171.google.com with SMTP id ho1so315473wib.16
        for <internals@lists.php.net>; Fri, 19 Sep 2014 16:20:21 -0700 (PDT)
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
         :cc:content-type:content-transfer-encoding;
        bh=QT8FXq3SGmnIJ1zDd1K9ZEoA74xz5Imhituc2+jHB04=;
        b=OCPkUHuCmgJsI++I06dXK0TfVW9Ed9EvEZOt6nkqExnEIuno3V/2TxR5XDVZGrAnsh
         aeUuDmt7qFLzAWIT2gX16skdiGwEAJqOoSr7EO1pyM2WOIxuoWs8J+Q+NQE4u4/e/18U
         2R+zNd1CrnbSIggGDj8wKLwkatfidUXolsibkc+6jHs1ml2H8gBiefKfqJGsQoH+rGi1
         nwvlhi1G0rkR+1GdFT59cvazpQ4FFpe76lG3K6qgoZDM0zIQf15NSoChOWyTNW0xglcH
         NYHzBsLyhYXQyqYvUL7Srku0EgSNzo18bTBWGPo1te8IbYSl3RYZTCs7fzWMll3CUT8Z
         c3JQ==
MIME-Version: 1.0
X-Received: by 10.180.206.230 with SMTP id lr6mr1240842wic.82.1411168821327;
 Fri, 19 Sep 2014 16:20:21 -0700 (PDT)
Received: by 10.217.55.195 with HTTP; Fri, 19 Sep 2014 16:20:21 -0700 (PDT)
In-Reply-To: <BA6704E0-4DFB-4E37-ACAB-F09210EE34D1@ajf.me>
References: <CAPwsocHm4wme7TDX-1hp=PdNGi0KzAwRz4RezW3KddV9_4m=JQ@mail.gmail.com>
	<B80686C1-F51D-462F-A4FA-4E8E6D92EED3@ajf.me>
	<CAPwsocHkobsmFoog4FJLws5EPCfeiaFkNybwSm_mWxoP-DJ85Q@mail.gmail.com>
	<BA6704E0-4DFB-4E37-ACAB-F09210EE34D1@ajf.me>
Date: Sat, 20 Sep 2014 00:20:21 +0100
Message-ID: <CAPwsocEfOKu4cnkRV8WSG3vCD_2ox3eoVf3iSq5k0HMptStb+w@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Loop... or...
From: leight@gmail.com (Leigh)

On 20 September 2014 00:15, Andrea Faulds <ajf@ajf.me> wrote:
>
> Why not? Python uses =E2=80=9Celse=E2=80=9D, and before creating this RFC=
 you initially wanted to use =E2=80=9Celse=E2=80=9D.

Then I realised it was folly. Documented in the RFC why "else" is a bad cho=
ice.

> I=E2=80=99m bringing it up because I think we=E2=80=99re only going to en=
d up with one feature or the other, and I think Python=E2=80=99s behaviour =
is more useful.
>

We can absolutely have both, but it's not for this RFC.