Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75385 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 491 invoked from network); 13 Jul 2014 08:16:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jul 2014 08:16:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; 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:56099] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/E1-14675-46042C35 for ; Sun, 13 Jul 2014 04:16:37 -0400 Received: (qmail 25573 invoked by uid 89); 13 Jul 2014 08:16:34 -0000 Received: by simscan 1.3.1 ppid: 25566, pid: 25569, t: 0.0720s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 13 Jul 2014 08:16:34 -0000 Message-ID: <53C24061.6050503@lsces.co.uk> Date: Sun, 13 Jul 2014 09:16:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <53C2178E.7070705@sugarcrm.com> In-Reply-To: <53C2178E.7070705@sugarcrm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening) From: lester@lsces.co.uk (Lester Caine) On 13/07/14 06:22, Stas Malyshev wrote: > It is very direct specification of > either strict parameter typing or coercive parameter typing. I don't > think using confusing terminology helps anything here. I think it was a > mistake to introduce this term from the start and we should stop > propagating it. It does come across as as an attempt to hide the 'strict parameter typing' which is something that is very much less attractive. If I wanted that then I'd simply switch back to C/C++ direct which is perhaps where we are now heading anyway with the increasing use of pre-compiled application code? One of the reasons I persist with PHP is the fact that many of my users can adjust the odd PHP file correcting sequence or modifying text without having to learn the intricacies of formal programming. It's adding all these complex layers that is taking PHP away from it's more novice friendly base ... If you want a formal programming language then just use one? -- 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