Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49346 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41131 invoked from network); 11 Aug 2010 15:30:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2010 15:30:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 ns.km36107.keymachine.de Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:55526] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 37/57-01618-612C26C4 for ; Wed, 11 Aug 2010 11:30:31 -0400 Received: from [192.168.1.31] (ppp-82-135-2-213.dynamic.mnet-online.de [82.135.2.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 78E2024E98; Wed, 11 Aug 2010 17:30:27 +0200 (CEST) To: Ryan Panning Cc: internals@lists.php.net, Lukas Kahwe Smith , Victor Bolshov In-Reply-To: <4C62BEFC.7070501@gmail.com> References: <1281478269.6608.292.camel@guybrush> <4C61D6D0.90907@sugarcrm.com> <4C62B9E0.4030305@gmail.com> <98F1C5D8-DA23-45B5-BA1F-F45B79CBC565@pooteeweet.org> <4C62BEFC.7070501@gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 11 Aug 2010 17:30:25 +0200 Message-ID: <1281540625.1132.39.camel@guybrush> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Strict typing From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Wed, 2010-08-11 at 10:17 -0500, Ryan Panning wrote: > 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? Yes. It was clearly said by quite many people that strict typing is so bad. Way clearer than almost any other decision. So please lets end this thread and move on to undecided questions. johannes