Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49343 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36211 invoked from network); 11 Aug 2010 15:17:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2010 15:17:20 -0000 X-Host-Fingerprint: 64.8.134.189 unknown Received: from [64.8.134.189] ([64.8.134.189:18652] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/56-01618-FFEB26C4 for ; Wed, 11 Aug 2010 11:17:20 -0400 To: internals@lists.php.net,Lukas Kahwe Smith Message-ID: <4C62BEFC.7070501@gmail.com> Date: Wed, 11 Aug 2010 10:17:16 -0500 User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 CC: Victor Bolshov References: <1281478269.6608.292.camel@guybrush> <4C61D6D0.90907@sugarcrm.com> <4C62B9E0.4030305@gmail.com> <98F1C5D8-DA23-45B5-BA1F-F45B79CBC565@pooteeweet.org> In-Reply-To: <98F1C5D8-DA23-45B5-BA1F-F45B79CBC565@pooteeweet.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 64.8.134.189 Subject: Re: [PHP-DEV] Strict typing From: rpanning@gmail.com (Ryan Panning) Lukas Kahwe Smith wrote: > ... > > anyway .. for the love of god, could be please stop arguing in circles, nothing .. really nothing that people brought forth pro/con any approach in regards to type checking/hinting whatever hasn't been mentioned on this list multiple times. > > ... I agree with you, another topic that has been debated to death here. Between this and the namespace separator debate, it's been hard to keep up. One other comment I forgot with my original post: Why not leave the choice (strict/weak) up to the end users by implementing both using the syntax I commented about? Is one way or the other so bad that it can't be implemented? At this point I feel like a decision should be made and stick with it. I would use this feature either way (strict/weak/both). It'll mainly be used in a framework so the users of that are going to have to deal with the end result. But if I had to vote it would be for weak. Thanks again.