Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9929 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69544 invoked by uid 1010); 18 May 2004 08:09:00 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 69146 invoked from network); 18 May 2004 08:08:58 -0000 Received: from unknown (HELO mx.thebrainroom.net) (65.200.24.98) by pb1.pair.com with SMTP; 18 May 2004 08:08:58 -0000 Received: by mx.thebrainroom.net (Postfix, from userid 517) id 7ACC414880BF; Tue, 18 May 2004 01:08:56 -0700 (PDT) Received: from BAUMBART (p508EBE13.dip.t-dialin.net [80.142.190.19]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx.thebrainroom.net (Postfix) with ESMTP id D3DE0148809B; Tue, 18 May 2004 01:08:49 -0700 (PDT) Date: Tue, 18 May 2004 10:06:51 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <197273668.20040518100651@marcus-boerger.de> To: Andrey Hristov Cc: Sara Golemon , internals@lists.php.net In-Reply-To: <40A9C2C8.3050508@hristov.com> References: <20040518040006.36155.qmail@pb1.pair.com> <40A9C2C8.3050508@hristov.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on jc.thebrainroom.net X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no version=2.63 X-Spam-Level: X-TBR-Filter: Virus scanned and defanged Subject: Re: [PHP-DEV] protected/private access and var_dump/print_r From: helly@php.net (Marcus Boerger) Hello Andrey, if we change something then we prevent all those function from showing private and protected values. The current situation is ok for me though. marcus Tuesday, May 18, 2004, 10:01:12 AM, you wrote: > Sara Golemon wrote: >> var_dump($someobject); shows only public properties (as I'd expect), but >> print_r($someobject) shows all properties (explicitly identifying >> protected/private props). >> >> Am I wrong in thinking that's not right? >> >> -Sara >> > print_r relies on a engine's routine while var_dump() does not. I had a patch to enable > var_dump do dump also the protected/private stuff (since I am var_dump() not a print_r() > fan). AFAIR Andrei was pro for var_dump() being consistent with print_r(). > http://www.hristov.com/andrey/projects/php_stuff/patches/var_dump.diff > The patch is from August last year. AFAIR it does what's expected :) > Andrey -- Best regards, Marcus mailto:helly@php.net