Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71386 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57260 invoked from network); 21 Jan 2014 21:50:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2014 21:50:25 -0000 Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.45 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.220.45 mail-pa0-f45.google.com Received: from [209.85.220.45] ([209.85.220.45:35284] helo=mail-pa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/13-40896-F9BEED25 for ; Tue, 21 Jan 2014 16:50:24 -0500 Received: by mail-pa0-f45.google.com with SMTP id lf10so6728585pab.4 for ; Tue, 21 Jan 2014 13:50:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NLqoFEgLWfZ9S9AMmbXKRrfXdljCSKTOazJsKKgPjag=; b=Mtu5qdfY1R3oeSDAFzs7L8CpUqnTF57sq7eO5sYf5fTJee6/NkqA1BGf1uayDLOfte B1AvUPGIXlG51EQCanlfwaVWCh0KRGqwtTAon35eNvNHrf1rUVyeTL73cfFm/nfAU0/t wGhpNZgsuO9g0IhAhn4Z1+RkE4Ks3yq7PxFT3yHdRrFK5ViwR6pHf8SC+auioVpK4zVc e60SdAAxfZVeMhQemBXYnPfc6quHrUt398iGFSGEx1/esAZDDdmjaUmKXQ5vpdwMC34P tvxwK4V9sWL7T7wvkPpKJJKYlW2NhlZPAi7kZml9Uh+wymheteMn5fNjGwXa78CrnQlM JrTQ== X-Gm-Message-State: ALoCoQkhYQc7eUJ/POi7qXiMg0QFXaI5Lvrd+ZscNSCSMh/iP1NUXWD1gVAbuo4bqWyd18/gnHFY MIME-Version: 1.0 X-Received: by 10.68.196.195 with SMTP id io3mr27812510pbc.6.1390341020487; Tue, 21 Jan 2014 13:50:20 -0800 (PST) Sender: php@golemon.com Received: by 10.70.77.164 with HTTP; Tue, 21 Jan 2014 13:50:20 -0800 (PST) X-Originating-IP: [2001:470:1f09:2fa:22c9:d0ff:fe87:295b] In-Reply-To: <1390340520.27607.73658653.3EB76580@webmail.messagingengine.com> References: <1390340520.27607.73658653.3EB76580@webmail.messagingengine.com> Date: Tue, 21 Jan 2014 13:50:20 -0800 X-Google-Sender-Auth: 2tDlNr81d0HjxL_Qp_uU1OwNmr8 Message-ID: To: Will Fitch Cc: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] [RFC] __debug_info() From: pollita@php.net (Sara Golemon) On Tue, Jan 21, 2014 at 1:42 PM, Will Fitch wrote: > On Tue, Jan 21, 2014, at 01:26 PM, Sara Golemon wrote: >> Something new to argue about: >> >> https://wiki.php.net/rfc/debug-info > > This is a really good idea. This will allow customization of the debug > info, and reflection to Reflection. That said, how/should this > functionality be integrated info Reflection? For example, > ReflectionClass::getDebugInfo()? > I think it'd make sense to add that as well, yes. Regardless of whether or not this RFC gets accepted, in fact. As to how, I'd treat that method just like getProperties() (Creating an array of ReflectionProperty objects), just from a different source. -Sara