Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96102 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75553 invoked from network); 22 Sep 2016 21:18:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Sep 2016 21:18:03 -0000 Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.217.169 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.217.169 mail-ua0-f169.google.com Received: from [209.85.217.169] ([209.85.217.169:36637] helo=mail-ua0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 48/52-59356-98A44E75 for ; Thu, 22 Sep 2016 17:18:02 -0400 Received: by mail-ua0-f169.google.com with SMTP id 15so13356828uai.3 for ; Thu, 22 Sep 2016 14:18:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v3+FI4RO8QJW3H1Gn1H2ie2g/TrBU5B5mgiHFtLhVIQ=; b=BBCI05Z4M7rcEgEvsX3X79J/jj1OWQ7ZqY+G1JwwVQ9wkr4wLm3cybuw6UULwjDIoB SWVXB4IaMq4xi/V+L1KCROUxSkeRKwFSUnA0M1scCDuQSzAw+E/7WWspcnmlRn6t3BfD LQBip2L2YOiA7GdEhg1hQUhROIuMbp9EISEIQs0wXi4j6Fu+Az4nznQgxXP9OYUCcGGC NeOZMfchfacjmNib8eNjpn3myZpnjrqQ2IjtEeelHHpOTxjwHGdpeNR9IeLj0IYhjiuP Fohl08/svZ0UrqhH+PFfzya5SQ5CNr1LvYvF3B6sAqljTy+jrWEOR1QNS57rrfYwPsTd VfoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v3+FI4RO8QJW3H1Gn1H2ie2g/TrBU5B5mgiHFtLhVIQ=; b=WsJnr1jxwoS8t2s35n0+peS0zQvlAHTczHq/HwC7bkm6vab695XGmwRoNcavSFY6Xz yxpa3XuJopWcDqL8HN3xDFmHqRWjUtfVJEImIAIxgHRZHrpcfATZu055PSi3zMEFKkNm ppxE+fzKaF1yN6aFScdmObVqi48c2WW1wy47ZPYzstE/MHldgfGXFmOfYWzVbgaT5hjE kN1cmqhp/8Wvvh30mnHe9NAu9llvqU8/1BZns3NvYPzqK5ovY1flmYvdPj4zJ2a+fsUt EjNKvrROa0Z3+7/cuhnzNTyWVTWjj2PMaDfwS9bydjYOQ/mxmz8GSlHg+9xVOvzVQoHj 2Afw== X-Gm-Message-State: AE9vXwMvZj/e1RVxTAlgVJD4ZnEXlDmsXvUGCPEyQYg3qOc3bjgIn0/l/0Wn0jrGolmpcgfM2hDi5RDnPN02Fw== X-Received: by 10.176.69.134 with SMTP id u6mr1617178uau.55.1474579078748; Thu, 22 Sep 2016 14:17:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.69.4 with HTTP; Thu, 22 Sep 2016 14:17:58 -0700 (PDT) X-Originating-IP: [2.99.239.160] In-Reply-To: References: Date: Thu, 22 Sep 2016 22:17:58 +0100 Message-ID: To: Vesa Kaihlavirta Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] RFC: Strict comparisons From: danack@basereality.com (Dan Ackroyd) > What still worries me personally is ===. What do you think would be the > least incorrect way to handle === > 2) === is not affected by strict_comparisons. I think not changing it is the correct thing to do.....but I think it needs more thinking about. Btw, the RFC would need to cover all cases of comparison. e.g. within for loops as well as if statements because: $initialValue = "2bananas"; for ($x=$initialValue ; $x<10; $x++) { echo "$x\n"; } cheers Dan