Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72530 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75626 invoked from network); 12 Feb 2014 21:52:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2014 21:52:59 -0000 Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.44 as permitted sender) X-PHP-List-Original-Sender: cryptocompress@googlemail.com X-Host-Fingerprint: 209.85.214.44 mail-bk0-f44.google.com Received: from [209.85.214.44] ([209.85.214.44:33634] helo=mail-bk0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4D/2A-19387-A3DEBF25 for ; Wed, 12 Feb 2014 16:52:58 -0500 Received: by mail-bk0-f44.google.com with SMTP id mz12so2852497bkb.3 for ; Wed, 12 Feb 2014 13:52:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GWodUvZnuRZ+6c+3d3NVUvBRPLpWYT2ITk5zKsKCkB4=; b=Tu/2uUI6yynQyDHQIgwlVOWPpO8Ipw5Oiaa+HfXRl7FBzp0DIqaSbgxgWxrRERU7W9 MctL72ZkD111nWhOpRiQ6MCgm6fSOgRoVfON1MQmT2bjB4boR5xu4qUfgTWcMpGYA7Qo UXSLlhER5NHqPOPAOjjhKrRAwfjIfrGOclvr3MJ8iSH2BIptKdqs2H+i6JGDqJzz85q3 HqY4TR+3Nhg4Lwtb7HKxeT8Q/DouzMFxlwj0kuZkzJ9nXnkF5mCd+ABb67FuAkeD3+8O FQYWGIHBMGQc/p+7km2rzrMkcujv3eFqnCogEhvXqVCDTYUEXIruvYTRhniFGSjSsioh xAeA== X-Received: by 10.204.201.74 with SMTP id ez10mr915bkb.83.1392241975640; Wed, 12 Feb 2014 13:52:55 -0800 (PST) Received: from [192.168.1.115] (mnch-5d872b07.pool.mediaWays.net. [93.135.43.7]) by mx.google.com with ESMTPSA id tf11sm56057bkb.17.2014.02.12.13.52.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 13:52:54 -0800 (PST) Message-ID: <52FBED22.4010706@googlemail.com> Date: Wed, 12 Feb 2014 22:52:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Rowan Collins , 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> In-Reply-To: <52FBE7FD.3050003@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [VOTE] __debugInfo() From: cryptocompress@googlemail.com (Crypto Compress) > 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? It's not easy nor fast to change X times __debugInfo() methods.