[xdebug-general] Re: Accessing private properties of object's ancestor using DBGp

From: Michal Gajek <migajek[@]gmail.com>
Date: Mon, 28 Dec 2009 10:19:31 +0100

in my opinion it is quite necessary. Lets say we have specific database
model class - which inherits after general database model - in most cases
the actual data is being stored in parent's class private property, and the
only way to access it is using __get / __set properties. Thus you won't be
able to see the loaded data of model using property_get, unless you do
var_dump which doesn't make any sense, as the idea of debugger is to avoid
var_dumping ...
It'd be very convenient to make this kind of preview working, otherwise in
many cases the debugger is completly unusable. This is not the opinion of
XDebug client developer, I'm rather saying it from my own experience - in
many cases I had to var_dump to see what data has been loaded to model /
controller, since XDebug shows empty variables...

In DBGp specs there is already show_hidden feature described ... what do you
think? :)

Best Regards / Pozdrawiam
Micha³ Gajek

2009/12/28 Derick Rethans <derick[@]xdebug.org>

> On Sun, 27 Dec 2009, Michal Gajek wrote:
> > some time ago I've filed bug report #494 however so far nobody
> > reviewed it, thus my question is - is that a known bug / missing
> > feature? I'd like to know that as I need to write docs to my DBGp
> > client dedicated to XDebug ...
> I started looking at bug #328 (http://bugs.xdebug.org/view.php?id=328)
> today which is about similar things. I'll have a look at #494 after
> this; however, I don't think that private properties of parents classes
> should be shown.
> regards,
> Derick
> --
> Like Xdebug? Send a postcard:
> http://derickrethans.nl/xdebug_2_released.php
> Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org
> twitter: @derickr and @xdebug
Received on Wed Dec 30 2009 - 10:55:31 GMT

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST