Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13348 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85825 invoked by uid 1010); 16 Oct 2004 19:13:53 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 85747 invoked by uid 1007); 16 Oct 2004 19:13:53 -0000 Message-ID: <20041016191353.85746.qmail@pb1.pair.com> To: internals@lists.php.net Date: Sat, 16 Oct 2004 16:13:51 -0300 Lines: 16 User-Agent: KNode/0.7.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Posted-By: 200.196.109.2 Subject: Type hints with null default values From: cunha17@uol.com.br (Cristiano Duarte) Hi @ll, Now that 5.0.3 is out, maybe it's time to bring back that old problem left in May: type hints and null default values. This feature was dropped since no one could come with a reasonable solution. So, for now, there is no (engine) way to have a parameter that can only be of some class or null. Am I right ? The use of null (I know it's not a value it's a type...) is justified because we don't have a "value" to represent a NULL OBJECT(or NO OBJECT). IMO, this is a necessary feature (maybe others thing this way too) and that's why I brought it back. Cristiano Duarte