Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83025 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35692 invoked from network); 18 Feb 2015 07:00:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Feb 2015 07:00:07 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.223.181 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.223.181 mail-ie0-f181.google.com Received: from [209.85.223.181] ([209.85.223.181:45418] helo=mail-ie0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/32-18888-47834E45 for ; Wed, 18 Feb 2015 02:00:06 -0500 Received: by iecat20 with SMTP id at20so46666969iec.12 for ; Tue, 17 Feb 2015 23:00:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=0xqoSeDwjVdfbMFrphcUFPKmRwzhd7A7j9mdMNnP6A4=; b=a6hN48l1Qu3q9/j7AwcxtfeJ85STfY4q0O+3e7y6blngPaRo09tMcZ3iKEFUDFmv0b dLePPxibWOYlwBcB8nKIVC7Ssi03PqpPygGSJjN2tYoEwpTleAMFmd+dSNl0vCTcYTyu wr0TqoNdKzcES3iml4FImxKgqXclYG8mr8riQpRN2w1byN9rvP1aP0oySKj3yC5qb7xS BLY5CX0vr+X3YPnt1riQk5RKfd/WtB9MfsXTBL4VXzU25fPC17TrmGYt8pfb7JanYAfy kvJ6T7PlmLfwHd39KzFLCKXiyZwRp9l3MyS334HswaHj+tee27TmejhBAAjiX/2ywx2g ulkw== X-Gm-Message-State: ALoCoQkpyLvDcrSkyp3o0+8Ei6PrCghTZsZjw7eEoVU7xHvmpb/kvajPqefM6mwtwPVpVD4kR8gaSBr7yXhtohngBGBEWtCKp15Vl4dzwazW1An3bmJp/W+nIjei1ySqH0AYaEdaH95YBmna3KaIPTJZvzwV9gYAGw== X-Received: by 10.51.16.1 with SMTP id fs1mr1195836igd.8.1424242801753; Tue, 17 Feb 2015 23:00:01 -0800 (PST) References: <54E3E27B.2010903@lerdorf.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKz6wpj8b81mnwJq1LfxWbU4ZJyQgGjcksIAbrU1N8Bn0wufZsGzLog Date: Wed, 18 Feb 2015 09:00:01 +0200 Message-ID: <2f99c47df51fa6c73131032ec50fade0@mail.gmail.com> To: Nikita Popov , Rasmus Lerdorf Cc: Sara Golemon , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] Scalar Type Hints v0.4 From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Nikita Popov [mailto:nikita.ppv@gmail.com] > Sent: Wednesday, February 18, 2015 3:06 AM > To: Rasmus Lerdorf > Cc: Sara Golemon; PHP internals > Subject: Re: [PHP-DEV] Scalar Type Hints v0.4 > > The inability to implicitly cast "123" to int is pretty much the KEY > distinction > between weak and strict scalar typehints (those pesky value-dependent type > checks). If the strict typing mode doesn't offer this, what's the point at > all? I am wondering what the point is indeed with preventing "123" to 123. So far, all the concrete use cases people brought up had to do with "Apple" or "100 dogs", but nobody ever seems to be able to explain why converting "123" to 123 is likely to be a problem real world. Is it really just static analyzers? Zeev