Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38422 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48958 invoked from network); 19 Jun 2008 18:07:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jun 2008 18:07:27 -0000 Authentication-Results: pb1.pair.com header.from=thekid@thekid.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=thekid@thekid.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain thekid.de from 212.227.126.183 cause and error) X-PHP-List-Original-Sender: thekid@thekid.de X-Host-Fingerprint: 212.227.126.183 moutng.kundenserver.de Received: from [212.227.126.183] ([212.227.126.183:64398] helo=moutng.kundenserver.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3D/D1-63224-D50AA584 for ; Thu, 19 Jun 2008 14:07:26 -0400 Received: from unterwegs (krlh-4dbd2ccf.pool.einsundeins.de [77.189.44.207]) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis) id 0ML25U-1K9OXX1AJ4-00010Z; Thu, 19 Jun 2008 20:07:19 +0200 Message-ID: To: "Sam Barrow" Cc: References: <46ccd1ab0804170742g142ed562t4f03339da549a820@mail.gmail.com> <02bb01c8cecc$76b73eb0$14b2a8c0@kartofel> <1213563678.12801.0.camel@desktop> Date: Thu, 19 Jun 2008 20:07:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 X-Provags-ID: V01U2FsdGVkX18+XUBUqdEvkPL9ZuITzxvpM5cfPK0a7Zm8rur jcHq6JYL1JCM/6xCIYSxDrsfHOjnynQDwAcipEE67KG/3cLwuP w9YC1ENTXVmTjirgpCfgD28oYJXKDre Subject: Re: [PHP-DEV] [RFC] Strict type hints (parameter and return value) From: thekid@thekid.de ("Timm Friebe") Hi, >> 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. Hrm, the Wiki states it does: http://wiki.php.net/rfc/typehint#bc_break1 If this can be worked out by other means, cool:) - Timm