Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84777 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52435 invoked from network); 14 Mar 2015 15:05:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Mar 2015 15:05: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:58202] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/00-52108-14E44055 for ; Sat, 14 Mar 2015 10:05:38 -0500 Received: (qmail 2050 invoked by uid 89); 14 Mar 2015 15:05:34 -0000 Received: by simscan 1.3.1 ppid: 2044, pid: 2047, t: 0.0753s 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.160.89.223) by mail4.serversure.net with ESMTPA; 14 Mar 2015 15:05:34 -0000 Message-ID: <55044E3E.4080603@lsces.co.uk> Date: Sat, 14 Mar 2015 15:05:34 +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: <550416BA.9070203@lsces.co.uk> In-Reply-To: <550416BA.9070203@lsces.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] A plea for unity on scalar types From: lester@lsces.co.uk (Lester Caine) On 14/03/15 11:08, Lester Caine wrote: > Lets simply get the ground rules on naming conventions and what is > reserved and the like to start the path to bigger things later? I'll ask yet again a question that I keep asking but not seeing anybody explaining. Just what is being added which PHP5 will actually baulk at? I've been assuming 'the type hints' and that it is adding these which will make a current library unusable with PHP5 systems? All of the discussion on just HOW the type hints are handled is secondary to the basic breaking of the code base? Once a third party has added type hints we have to handle the results, which may be different depending on how the 'user' of type hint expects it to be interpreted? Weak or Strict will fail in different ways? But of more interest, just what happens if I pick up a library that has been 'improved' by the inclusion of strict types but I'm still working with no typing at all? Or rather legacy type checking as part of the code base. The code base I will be running myself with PHP7 is PHP5.4 with E_STRICT etc. clean code. That is what the test bed is comparing and with what has been added so far the code simply works, and I expect THAT to be the case but I keep seeing things which suggest I will HAVE to make changes to the PHP5.4 code for it to run clean on PHP7 by the time we get to RC stage? -- 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