Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42947 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89013 invoked from network); 5 Feb 2009 19:58:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2009 19:58:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 83.243.58.133 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 83.243.58.133 mailout1.netbeat.de Linux 2.6 Received: from [83.243.58.133] ([83.243.58.133:51968] helo=mailout1.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/50-16965-5B34B894 for ; Thu, 05 Feb 2009 14:53:26 -0500 Received: (qmail 2217 invoked by uid 89); 5 Feb 2009 20:05:26 -0000 Received: from unknown (HELO ?192.168.1.103?) (johannes%schlueters.de@93.104.114.3) by mailout1.netbeat.de with ESMTPA; 5 Feb 2009 20:05:26 -0000 To: Sebastian Bergmann Cc: internals@lists.php.net In-Reply-To: References: <5EC76153-898F-49C2-BDF1-C227578DB874@pooteeweet.org> <298CA3D0-60B7-4CFD-A2D3-E39D52ECDD46@bitextender.com> <1233851543.8601.24.camel@goldfinger> <1233860567.8601.34.camel@goldfinger> Content-Type: text/plain; charset="UTF-8" Date: Thu, 05 Feb 2009 20:53:18 +0100 Message-ID: <1233863599.8601.42.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] towards the next 5.3 release From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2009-02-05 at 11:06 -0800, Sebastian Bergmann wrote: > Johannes Schlüter wrote: > > Of course we could, we'd "just" have to change a structure and > > zend_verify_arg_class_kind() and of course the language syntax to allow > > something like "function foo(A|B $bar) {}" but this still would mean to > > This should, of course, only be for built-in functions and methods. But > yeah, it probably does more harm than good. Doing this for built-in stuff won't help the issue here is about overloading an internal method. So we'd have to give it to userland. > It just sucks, IMHO, that some functions and methods will not have > Reflection API metadata because the same arginfo structure is used for > two things. But I will shut up now. So reflection should use other data than the engine thus leading to inconsistencies? Reflection's purpose is to give the engine's information to userland ... johannes