Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18448 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48855 invoked by uid 1010); 25 Aug 2005 22:02:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 48840 invoked from network); 25 Aug 2005 22:02:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Aug 2005 22:02:50 -0000 X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from ([212.112.227.169:53780] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id A2/D1-28235-7004E034 for ; Thu, 25 Aug 2005 18:02:48 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 86F00DF00C0; Fri, 26 Aug 2005 00:03:03 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (ipx11223 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32322-04; Fri, 26 Aug 2005 00:03:00 +0200 (CEST) Received: from [127.0.0.1] (i577B6050.versanet.de [87.123.96.80]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 5E882DF005C; Fri, 26 Aug 2005 00:02:59 +0200 (CEST) Message-ID: <430E3FFF.8020304@php.net> Date: Fri, 26 Aug 2005 00:02:39 +0200 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derick Rethans Cc: PHP Developers Mailing List , Jan Borsodi , Raymond Bosman , Frederik Holljen , Tobias Schlitt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] Property Overloading RFC From: lsmith@php.net (Lukas Smith) Derick Rethans wrote: > On Tue, 2 Aug 2005, Derick Rethans wrote: > I updated the proposal: > http://files.derickrethans.nl/property_overloading.html 1) seems to be an issue in doxygen and phpDocumentor 2) this seems solveable with a non public set of arrays containing information about the property and its visibility .. with a bit of hacking phpDocumentor could even read this information if they/we decide on a suggested nameing standard. i dont see why we should pollute the php language with this though 3) sounds like a great idea. we should also have something like this for __call(). regards, Lukas