Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82969 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31301 invoked from network); 17 Feb 2015 15:03:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 15:03:57 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:47979] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/38-19463-95853E45 for ; Tue, 17 Feb 2015 10:03:54 -0500 Received: (qmail 19751 invoked by uid 89); 17 Feb 2015 15:03:50 -0000 Received: by simscan 1.3.1 ppid: 19745, pid: 19748, t: 0.0736s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 17 Feb 2015 15:03:50 -0000 Message-ID: <54E35855.4060906@lsces.co.uk> Date: Tue, 17 Feb 2015 15:03:49 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <011801d04a07$83ab1c00$8b015400$@php.net> <016f01d04a3a$e9183220$bb489660$@php.net> <022801d04ab1$4a0c47d0$de24d770$@php.net> <1913e09d7f52541901d8574d2080a63f@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reviving scalar type hints From: lester@lsces.co.uk (Lester Caine) On 17/02/15 14:49, Andrey Andreev wrote: >> I agree. It's more of a question of eliminating potentially dangerous >> > conversions than just being lossless. >> > > Agreed as well. However, while bool -> int conversion one of the > reasons why many people want strict type-hints, it also often makes > sense and is quite widespread. There's no silver bullet for that > problem. Returning 'not-zero/empty' as true and 'zero' as false is one of the natural things to use in PHP and I don't think any other language has that flexibility? It is also why some of the other 'little changes' such as hard coded IS_TRUE and IS_FALSE are actually somewhat alien! Certainly is does not play well with my methods of working, but then I prefer a function to return a result rather than crash out with an exception ... Although -ve values are even more useful than a simple 'zero' return and that may replace a string return. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk