Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49383 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12234 invoked from network); 11 Aug 2010 20:59:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Aug 2010 20:59:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=phpwnd@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=phpwnd@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: phpwnd@gmail.com X-Host-Fingerprint: 74.125.83.170 mail-pv0-f170.google.com Received: from [74.125.83.170] ([74.125.83.170:63430] helo=mail-pv0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AF/85-18548-32F036C4 for ; Wed, 11 Aug 2010 16:59:16 -0400 Received: by pvg16 with SMTP id 16so246064pvg.29 for ; Wed, 11 Aug 2010 13:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TuWCWV9twjuqCPyxbiSl9LHzjbC64h6syPDrplIn4js=; b=xFdvef3tBoe9X26udOEJrZAjAU2IAbmbL7icBs0Me5Xj7WCLfuh/Ml9Low0saIEmZO 5+rP8z8ncvzNKuxDbXBv3RQ3Im8zI8qSjZN3JQGNY+I6ltqI3hF9hNmQmL50F6zNCidm fU7hmYoQehx3k+xHQpaHCahZakByN5yBX3zEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Nm3vQ85keBJeP+3kx4RXFXgEQ6sqMkEDtjzVtrbp34JiOUF5aVeC2sSyRRIrSboCDG 9lhvficFTzdsJE4s/KSe4fbc9BmFktdqo04RvteT98ZNNdZeybMPcqCNbqVLvs2/fezi t+1HonE0kfxp2eLGg8cwO53dUiXq/pbKU1C34= MIME-Version: 1.0 Received: by 10.114.106.14 with SMTP id e14mr22624216wac.51.1281560353031; Wed, 11 Aug 2010 13:59:13 -0700 (PDT) Received: by 10.114.154.9 with HTTP; Wed, 11 Aug 2010 13:59:12 -0700 (PDT) In-Reply-To: <7.0.1.0.2.20100811225519.0ef42c40@zend.com> References: <1281478269.6608.292.camel@guybrush> <4C61E5CA.5070604@sugarcrm.com> <4C61F3EF.5030409@sugarcrm.com> <4C6241D1.6030909@sugarcrm.com> <4C62DBE9.7090008@sugarcrm.com> <7.0.1.0.2.20100811213714.1540f338@zend.com> <7.0.1.0.2.20100811225519.0ef42c40@zend.com> Date: Wed, 11 Aug 2010 22:59:12 +0200 Message-ID: To: Zeev Suraski Cc: Stas Malyshev , Internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Strict typing From: phpwnd@gmail.com (Josh Davis) On 11 August 2010 21:59, Zeev Suraski wrote: > Consensus about what? =A0About two similar features with slightly differe= nt > syntax being a bad thing? =A0I don't think we need consensus for that. = =A0That's > not up for discussion. =A0It's an axiom for PHP. Of course it depends on your definition of "similar features." One feature checks the type of an argument, the other checks the value of an argument and casts it to another type if necessary. I see it as serving two different applications, just like =3D=3D and =3D=3D=3D are mean= t for different things despite being two similar operators. > See above. =A0It would do everyone good if they don't just think about > themselves and whether they're fine or not with a given feature, but abou= t > the impact it would have on the userbase at large. Not sure what kind of impact we're talking about here. Currently, there's no scalar type hinting and there will never be a consensus around strict XOR weak. Having an implementation that allows both while reusing a familiar syntax (parentheses as a way typecast) looks like the best (and perhaps only) way to move on.