Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84769 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32006 invoked from network); 14 Mar 2015 11:08:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Mar 2015 11:08:47 -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:45874] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/50-29409-DB614055 for ; Sat, 14 Mar 2015 06:08:46 -0500 Received: (qmail 10013 invoked by uid 89); 14 Mar 2015 11:08:42 -0000 Received: by simscan 1.3.1 ppid: 10005, pid: 10010, t: 0.0734s 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; 14 Mar 2015 11:08:42 -0000 Message-ID: <550416BA.9070203@lsces.co.uk> Date: Sat, 14 Mar 2015 11:08:42 +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: In-Reply-To: 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 13/03/15 23:48, Arvids Godjuks wrote: > And actually, I would plea for a moment of sanity right now. > > As far as i'm concerned - the RM for the 7.0 had to step in a long time ago > and said "guys, I do not accept any typehint proposals into the 7.0 > release, work it out and come back for 7.1". > Because if this would be a commercial development before a release - > feature would be scrapped and re-sheduled for later release. > Why? Because the clusterf**k happened at RFC level already, the development > itself is going to be haisty considering the timeline and definetly being > bombarded by the protesters, countless critisism and so on. It is going to > affect the projects. And that is a bad thing. Look past the damn typehint > RFC's and just try to asses the big picture. Right now it's a tunnel vision > for many on the list. Seconded ... There are more important things to get right, so perhaps just protecting the hooks for type hints is the best that can be fully supported in PHP7 ? Lets simply get the ground rules on naming conventions and what is reserved and the like to start the path to bigger things later? -- 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