Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107694 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 70935 invoked from network); 25 Oct 2019 12:40:20 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 25 Oct 2019 12:40:20 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 9771D2C0524 for ; Fri, 25 Oct 2019 03:26:58 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: X-Spam-Virus: No Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Fri, 25 Oct 2019 03:26:58 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id c2so1679509wrr.10 for ; Fri, 25 Oct 2019 03:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UPIwmHRs3O9bK1IJieYcuTI/3TZZ/fSwM++Zjn21Ha0=; b=P8JGZ/l9i5gDmoKkFf85EJEGOMdZ7ssCRpXUgyHlLhU4XTD4iGcLTmUitfZ5IjV6jc ElmMn9i0g4RiO+vbw7jXShc3O41cD4rneoioUMOA1Yf4gPDBf9EMs/9CfM9oEcIrpEfK gr7pHZq2tqTGrLxWl3SfUBtngphi0kcgY0KQDpmBvHrrU2dQE3FWsGAQn49gWRsY3ERX k1lkxvGz3DKAVV+ypsKx0DlMQpmoziITKV1kE5y8r4rPx1wSn4T5vGxlAVAF5V96Rj2U x6q0M6Upc6/rlYtkkZ133T7ps3+vYOQo7E6IK2oyKt5RWNeOJyooAw+7cP+cKqw1QDiC zcpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UPIwmHRs3O9bK1IJieYcuTI/3TZZ/fSwM++Zjn21Ha0=; b=HamQ06m05+Ozl3GwyC6Bow+25PSlL7eaWiiijHgQ24sfNSYmBRhrYlKdWsk2i+ejZN HlNKw3UNK6drlEPAuuIWr25bsin/rll1yQLKJzi+Y+H58mpfXbYlRaFpzL3ELc3nv7Lm TIwOkZPqsywCJX97NA65olFjiMTFPExap83I/6U0C/V2ygdNxasZzmKwAtF417R5CsVt CZxOFQHLIgrcUnqlaxdezNjo0ViQMZKMY+nWuRz2QXR/9hTHLuxn8XCuHemkao+nr4OE LLhyO8/YyzHbOx322+Q4mgRNTobBAzJr3PundZSRt7IIsVSXYfE9rgQ0Go32hiui5NvS 511Q== X-Gm-Message-State: APjAAAXJ5t2oa7Sb55oJ71SP1zedSVVWj8/x9MgFiJp2LnvU034Po09Z Pw7KLS72T1u+VMthJPB48II= X-Google-Smtp-Source: APXvYqxGhzhr5R9vzvDwHzIo2y1VTVovZ5GA0yij1zayMso8EIJrV1GrbyEAXdyY0uWnX9UlMkgaLA== X-Received: by 2002:adf:e50a:: with SMTP id j10mr2199760wrm.352.1571999217202; Fri, 25 Oct 2019 03:26:57 -0700 (PDT) Received: from [192.168.0.63] (84-75-30-51.dclient.hispeed.ch. [84.75.30.51]) by smtp.gmail.com with ESMTPSA id t185sm735135wmf.45.2019.10.25.03.26.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Oct 2019 03:26:56 -0700 (PDT) Message-ID: <751CC090-C847-4ED7-969F-0680AFF7C3B5@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_6142B329-CCB8-4835-9E2C-31D236AA88AA" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Fri, 25 Oct 2019 12:26:55 +0200 In-Reply-To: Cc: Ken Stanley , Kosit Supanyo , Bruce Weirdan , PHP internals To: Sara Golemon References: X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator From: claude.pache@gmail.com (Claude Pache) --Apple-Mail=_6142B329-CCB8-4835-9E2C-31D236AA88AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Le 25 oct. 2019 =C3=A0 01:23, Sara Golemon a =C3=A9cri= t : >=20 > Just testing the waters: Is there any appetite to have AND and OR = behave > more like Pythons operator? > Instead of now: > (a or b) =3D> bool(true) if either of a or b are true > (a and b) =3D> bool(true) is either of a or b are true >=20 > Behave as: > (a or b) =3D> Value of a if true, b if a is not true but b is, = bool(false) > otherwise. > (a and b) =3D> Value of b if both are true, bool(false) otherwise. >=20 Besides BC concerns, it is probably not a good idea to introduce (more) = subtle differences between `and` and `&&`. That is, if you change `and`, = you should change `&&` in the same direction. Maybe simply introduce the `!?:` operator?... Nevermind. =E2=80=94Claude= --Apple-Mail=_6142B329-CCB8-4835-9E2C-31D236AA88AA--