From andre.zege at gmail.com  Fri Apr  8 17:38:12 2011
From: andre.zege at gmail.com (A Zege)
Date: Fri, 8 Apr 2011 08:38:12 -0700 (PDT)
Subject: [Rd] How to debug reference classes?
In-Reply-To: <3D59DF35E7CF3E42BA70C23BD5CBE6A85F42B80C69@exvic-mbx04.nexus.csiro.au>
References: <1302202852028-3434269.post@n4.nabble.com>
	<3D59DF35E7CF3E42BA70C23BD5CBE6A85F42B80C69@exvic-mbx04.nexus.csiro.au>
Message-ID: <1302277092995-3436674.post@n4.nabble.com>

Thank you very much, gentlemen. It seems reference classes will make my life
much easier. I won't pretend that i fully understand the wizardry with
environments that you do, but it works :). Namely the steps to mtrace a
class method by doing what John and Mark outlined
   xx$edit<-xx$edit
   mtrace(edit, from=xx)
   xx$edit(1,1,99)

do the magic of starting mtrace which solves my problem for practical
purposes. I was not able to make the second part of prescription related to
debugging unconstructed objects work. Namely, whenever i do 

 mtrace( edit, from=mEditor$def at refMethods) 

I get 
Error in parent.env(from) : the empty environment has no parent. Must be
doing something wrong, but haven't yet figured what.

--
View this message in context: http://r.789695.n4.nabble.com/How-to-debug-reference-classes-tp3434269p3436674.html
Sent from the R devel mailing list archive at Nabble.com.



[Rd] How to debug reference classes?
A Zege