Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38244
Return-Path: <thekid@thekid.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 67966 invoked from network); 15 Jun 2008 09:45:00 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 Jun 2008 09:45:00 -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.179 cause and error)
X-PHP-List-Original-Sender: thekid@thekid.de
X-Host-Fingerprint: 212.227.126.179 moutng.kundenserver.de  
Received: from [212.227.126.179] ([212.227.126.179:58796] helo=moutng.kundenserver.de)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 98/29-06776-994E4584 for <internals@lists.php.net>; Sun, 15 Jun 2008 05:44:58 -0400
Received: from kartofel (krlh-4dbdd31b.pool.einsundeins.de [77.189.211.27])
	by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis)
	id 0MKwtQ-1K7on81qjR-0004Yy; Sun, 15 Jun 2008 11:44:54 +0200
Message-ID: <02bb01c8cecc$76b73eb0$14b2a8c0@kartofel>
To: <internals@lists.php.net>
References: <46ccd1ab0804170742g142ed562t4f03339da549a820@mail.gmail.com>
Date: Sun, 15 Jun 2008 11:44:53 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX1/bfXpzY7HqLdewqDDaxRf23LGWLNxFawb1zp5
 KbubWNyoJl5Qc79hT+DZmrC6H9O0V2r0391kkZjCnijwovMsWH
 TW8J27CFv45TigSEhmHpg==
Subject: Re: [PHP-DEV] [RFC] Strict type hints (parameter and return value)
From: thekid@thekid.de ("Timm Friebe")

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.

http://www.google.com/codesearch?q=class+Object+lang%3APHP&hl=en

- Timm