Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72531 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77564 invoked from network); 12 Feb 2014 22:08:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2014 22:08:30 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.182 mail-wi0-f182.google.com Received: from [209.85.212.182] ([209.85.212.182:48204] helo=mail-wi0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FB/8A-19387-CD0FBF25 for ; Wed, 12 Feb 2014 17:08:29 -0500 Received: by mail-wi0-f182.google.com with SMTP id f8so7674507wiw.15 for ; Wed, 12 Feb 2014 14:08:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=HRewi0yCogUdKEjqF0Vmna799lpgFbes/s279btwEu4=; b=Cg3A3zyIAMmrc0z0DdAI5zOVJySRr65yUg91CMQb9UMxmeLsKb648IeHvwNgZev4lU QH7/1I4SDMu11ebZJ0GuNk80eKe0QhVzYmzMWYko+e05Cvu1qMAxVE3ggJitU3xfIFu7 +XTsTPlQ2100rFtH6s1GW3NV+k2til2hEYbkvRTgHaHcpnUiJtv6Sf1aloet5ncdCfFR DwGb1KJ7cBJU+NQigJGSQHfYBX1HRRXIVhhk2WpEBdw3MRS3rke9l37zgxCP+FUs51C7 VNMP5UD5Y4YSgemYFtmwUzr/ul6cxgLkRKXh5v6EyT5hTWLWLxBufPXQrHUTaX8lP2ZM FwLw== X-Received: by 10.180.165.174 with SMTP id yz14mr3893892wib.34.1392242905309; Wed, 12 Feb 2014 14:08:25 -0800 (PST) Received: from [192.168.0.152] ([62.189.198.114]) by mx.google.com with ESMTPSA id q2sm55416244wjq.0.2014.02.12.14.08.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 14:08:24 -0800 (PST) Message-ID: <52FBF0D7.2020704@gmail.com> Date: Wed, 12 Feb 2014 22:08:23 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: PHP Developers Mailing List References: <52F00437.7010903@googlemail.com> <52FA71FE.8060808@googlemail.com> <1392151967.3990.11.camel@guybrush> <52FA90B3.5040205@googlemail.com> <1392153156.3990.13.camel@guybrush> <52FA99C4.5080006@googlemail.com> <1392155891.3990.15.camel@guybrush> <52FA9FD3.6000008@googlemail.com> <52FBDC4D.9020302@googlemail.com> <52FBE7FD.3050003@gmail.com> <52FBED22.4010706@googlemail.com> In-Reply-To: <52FBED22.4010706@googlemail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [VOTE] __debugInfo() From: rowan.collins@gmail.com (Rowan Collins) Crypto Compress wrote (on 12/02/2014): > >> It still feels to me that someone debugging the implementation of the >> object, rather than its interaction with the system, would have >> plenty of opportunity to by-pass / remove the hook anyway. > > What about a phar? My point was that if you're debugging the *implementation*, you're going to be looking at the source tree, not the distribution. If you're looking at a distributed version, your main interest is in how to *use* the objects, which the maintainer can give you hints for via __debugInfo() > It's not easy nor fast to change X times __debugInfo() methods. True. I can't really picture somebody adding carefully crafted methods to every class they write, though; more likely, it will be defined in some ancestor class, or maybe even a trait, so you'd change it there, and the whole object graph would go back to "normal". I guess generated code might include it, but then you'd probably have the option of re-generating it without (again, if you were interested in the *implementation* of the objects, rather than just the *use* of them). Regards, -- Rowan Collins [IMSoP]