Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78257 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19694 invoked from network); 22 Oct 2014 22:34:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2014 22:34:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.181 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.220.181 mail-vc0-f181.google.com Received: from [209.85.220.181] ([209.85.220.181:65368] helo=mail-vc0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/E9-63701-8E038445 for ; Wed, 22 Oct 2014 18:34:17 -0400 Received: by mail-vc0-f181.google.com with SMTP id le20so2636632vcb.40 for ; Wed, 22 Oct 2014 15:34:14 -0700 (PDT) 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=WIkz4TJT1Hj/KZoYcOI/XFHDt1rmXWBeAXvQ4LHVKqA=; b=jxozwk/bvIhvzwlXTAx1j2LRjyL6dub8wdWBOkn6ABvAV5Qr0VNKkaPXNUSLNV5iQp c4+yrLxX+Xf+7ZHaOwj1RzFzwjT+qndN09Wa/6KjjJH7uP1B4YvPsMuNoEu0H8eNIegz UFqPvMX07WlPN6Hkj6Z3cSF1cn66fzduy4EH6NesM2hkVeO4t0OcD6HavR7wL+9J5YxW rXsUT2sMCodei41Q4e/7/wL5oruGFX4RIf9tu0lfVSi4O+dcYIV677A4UHp7pf71g6KB /2czHiT7VClZyLH86NHv86dmZSdpCzwEi8Z6GHqdYNm2RDUEP850300bd3EnesYtA/t5 6okg== X-Gm-Message-State: ALoCoQlljlGyDsQl87sDdvW6+k+eYsNnYsHVwJ9gopEPzaDy2qP4hmRFwau0Q+xqsrA/OMV8DuIu5gO4bEBQfBnXMBTuDlBsXiVlzBE9Km/zF6JnrIQLmKjrW2NXTSlU8Sv/twuMiYGu5imKolo5WT65LrVtFnissg== X-Received: by 10.220.123.3 with SMTP id n3mr747981vcr.46.1414017254565; Wed, 22 Oct 2014 15:34:14 -0700 (PDT) References: <66B7B28C-2651-4A71-AC2A-55D4C7BB3DDC@ajf.me> <866A39C7-6F11-408D-8BCA-594BA22E8569@ajf.me> <5447682B.2080100@sugarcrm.com> <019325A5-4F82-4179-B4D7-29E5649B2616@ajf.me> <77c09d71b5ee91245640e414c320518d@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJkwG276Wk0Upx97kt7WiAQcULrfAGSwBqnAi5QI8QCGl+NrgJ4wNJWAjMdez4Bx3YEnAG0K5AzmqL2T5A= Date: Thu, 23 Oct 2014 01:34:13 +0300 Message-ID: To: Andrey Andreev Cc: Andrea Faulds , Stas Malyshev , Dmitry Stogov , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] [RFC] Safe Casting Functions From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Andrey Andreev [mailto:narf@devilix.net] > Sent: Thursday, October 23, 2014 1:15 AM > To: Zeev Suraski > Cc: Andrea Faulds; Stas Malyshev; Dmitry Stogov; PHP Internals > Subject: Re: [PHP-DEV] [RFC] Safe Casting Functions > > > While it doesn't explicitly say so, it's clear that one of the goals > > of the RFC is make it easier for a 'strict typing' RFC to be accepted > > in the future. This is a clear indication this constitutes a > > fundamental > change to the core language. > > I'd argue that it has the exact opposite goal - to be able to say "use > to_string(), to_int(), etc; we don't need strict type hinting". You may be right, I may have misinterpreted the rationale - but I think the consequences are still the same. If this (in the eyes of the author) undoes the need for a feature as fundamental as strict typing, how can it be just a bunch of simple functions? Zeev