Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38262 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86664 invoked from network); 15 Jun 2008 21:01:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2008 21:01:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=sam@sambarrow.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=sam@sambarrow.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sambarrow.com from 208.70.128.73 cause and error) X-PHP-List-Original-Sender: sam@sambarrow.com X-Host-Fingerprint: 208.70.128.73 smtp-gw47.mailanyone.net Received: from [208.70.128.73] ([208.70.128.73:55514] helo=smtp-gw47.mailanyone.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 07/1E-06776-E0385584 for ; Sun, 15 Jun 2008 17:01:05 -0400 Received: from mailanyone.net by smtp-gw47.mailanyone.net with esmtpsa (TLSv1:AES256-SHA:256) (MailAnyone extSMTP sam@sambarrow.com) id 1K7zLP-0000il-VN; Sun, 15 Jun 2008 16:01:00 -0500 To: Timm Friebe Cc: internals@lists.php.net In-Reply-To: <02bb01c8cecc$76b73eb0$14b2a8c0@kartofel> References: <46ccd1ab0804170742g142ed562t4f03339da549a820@mail.gmail.com> <02bb01c8cecc$76b73eb0$14b2a8c0@kartofel> Content-Type: text/plain Date: Sun, 15 Jun 2008 17:01:18 -0400 Message-ID: <1213563678.12801.0.camel@desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Strict type hints (parameter and return value) From: sam@sambarrow.com (Sam Barrow) On Sun, 2008-06-15 at 11:44 +0200, Timm Friebe wrote: > Hi, > > > If anyone wants use type hinting, i believe that it should be strict. > > Otherwise, it makes more sense to not use it. > > I like this generally, but cannot live with the BC issues raised. > Introducing all type names as keywords will make "class Object", "class > Integer" and so on give a syntax error. > That's actually not true, the patch does not introduce new keywords. > http://www.google.com/codesearch?q=class+Object+lang%3APHP&hl=en > > - Timm > >