[xdebug-general] Re: isset & empty not shown in traces

Le jeudi 03 mai 2007 à 16:52 +0200, Derick Rethans a écrit :
> On Thu, 3 May 2007, Yannick Warnier wrote:
>
> > Le jeudi 03 mai 2007 à 09:05 +0200, Derick Rethans a écrit :
> > > On Wed, 2 May 2007, Sean Coates wrote:
> > >
> > > > Yannick Warnier wrote:
> > > > > Hello,
> > > > >
> > > > > I'm using xdebug 2.0.0 RC3. Is there a reason why calls to isset() and
> > > > > empty() are not reported in traces?
> > > >
> > > > I suspect for the same reason that instanceof and == are not shown in
> > > > traces (they're not actual functions).
> > >
> > > That is correct, isset() and empty() are language constructs in PHP.
> >
> > OK, thanks to both.
> > I suppose the classic way of getting around that (if needs be) is to
> > write a wrapper function like
> > function myisset($var){return isset($var);}
> > which I did and it worked fine (but you have to replace all the isset()
> > calls by myisset() calls in the script that worries you).
>
> Another possibility would be that I overload those opcodes (if possible)
> and expose them as function calls. I am not sure how possible this is
> though. Feel free to file a feature request at http://bugs.xdebug.org so
> that I can have a look at it for after 2.0 has been released.

Filed here http://bugs.xdebug.org/bug_view_page.php?bug_id=0000264
Don't know your standards for filing feature requests but I've put a
severity of "normal". Sorry if it's too high. "tweak" didn't feel right,
somehow.
Received on Thu May 03 2007 - 19:53:11 BST