Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58211 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87270 invoked from network); 27 Feb 2012 22:41:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2012 22:41:31 -0000 Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.29 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.29 out5-smtp.messagingengine.com Received: from [66.111.4.29] ([66.111.4.29:59398] helo=out5-smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/52-11273-A960C4F4 for ; Mon, 27 Feb 2012 17:41:31 -0500 Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1D1DD211AF for ; Mon, 27 Feb 2012 17:41:28 -0500 (EST) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 27 Feb 2012 17:41:28 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=WzExA+Vg3rfPB3K5bbNzOM bwsio=; b=LBBrxvUqYXKGtFlZpG/fPwSM9E4QQiCBrQ74uJAtEtAK29Ku8WOFZz hai94L2dcvZodpftouAznhMCRzXWzTAobzpebXdnCqt/U6B91onl/2DiwSZpYM1O rf6EHuHdrFLj/KpLm5+56vhofETzvQHQl5dUmH4qMuxJqxDd/9Xac= X-Sasl-enc: gXGeKesKszHLQJObFPymupiSLkGjk0TjvWWN8QjigLI+ 1330382487 Received: from garfield.ad.palantir.net (unknown [209.41.114.202]) by mail.messagingengine.com (Postfix) with ESMTPSA id DDCFB482516 for ; Mon, 27 Feb 2012 17:41:27 -0500 (EST) Message-ID: <4F4C0697.5060706@garfieldtech.com> Date: Mon, 27 Feb 2012 16:41:27 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: internals@lists.php.net References: <1330357150.2159.30.camel@guybrush> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Scalar type hinting From: larry@garfieldtech.com (Larry Garfield) That's going to get turned into the "real" name if used. I suggest instead: Gribblefritz. Gribble typing: the type handling that PHP does today in 5.3/5.4 for scalar values. Fritz typing: Some as-yet-undefined type handling that is pickier than Gribble typing, but how much pickier is unclear. That, at least, no one has any pre-conceived definition of. --Larry Garfield On 2/27/12 4:31 PM, Kris Craig wrote: > Would "firm" work better? > > --Kris > > > On Mon, Feb 27, 2012 at 2:27 PM, John Crenshawwrote: > >>> -----Original Message----- >>> From: Kris Craig [mailto:kris.craig@gmail.com] >>> >>> Now, to rewind a bit past the latest chunk of "I hate this idea" >> posts.... >>> >>> I'd like to suggest a new term: "strong". >>> >>> This term would be similar to "weak", except with a few key differences: >>> >>> ... >>> >>> Some possible examples of how this would look: >>> >>> weak int $i = "aaa"; // Converts to 1 and throws a warning. >>> strong int $ii = "aaa"; // Throws a fatal error. >>> weak int $i = "1"; // Converts to 1. >>> strong int $ii = "1"; // Converts to 1. >>> >>> >>> --Kris >> >> Can we use a different word (not "strong") at least for just discussion >> purposes? I worry that "strong" will produce a feeling of intense fear and >> anxiety in people who have been burned out by strict typing debates. The >> words "strong" and "strict" are basically inflammatory at this point. In >> the interest of facilitating a reasonable discussion, I think we should >> avoid language that is likely to cause discussion to break down. >> >> John Crenshaw >> Priacta, Inc. >> >