Dirk, thanks for your reply. I posted my answer right away and went on
vacation. My post was pending since then. Still cannot post, so I opened
another profile -- maybe this time it gets through.
To answer your questions, I run R-2.12.1 on 64 bit RedHat Linux on Xeon
machine.
What seems odd that
Apologies for asking something that is probably super obvious, i just started
with S4 classes and i guess i am not finding documentation that layout the
grammar rules and give enough examples. Some questions i am having are these
1. I understand that main method of writing a member function is to
Apologies for asking something that is probably very obvious, i just started
with S4 classes and i guess i am not finding documentation that lays out the
grammar rules and gives enough examples.
I understand that main method of writing a member function is to write a
generic function and setMetho
This looks awesome -- it is precisely what i wanted. I have started hacking
with passing around environments to simulate behavior of classes i was
after, but this is so much neater. Reference classes seem to do precisely
what i wanted. Thank you very much.
--
View this message in context:
http:/
How do you debug methods of a reference class? I've been using mtrace, which
is excellent, but i cannot figure out how to mtrace a reference class
method. Maybe there is some other way to debug these, for example with
ordinary trace? for now i am only able to use options(error=recover), which
is no
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
I am trying to define subset operator for a reference class and hitting some
problem i am unable to diagnose.To give an example, here is a toy class
generator that is a wrapper around a list
tmpGEN<-setRefClass("TMP", fields=list(
namelist="list"
I'd like to have a version of a package that doesn't include sources. I
thought that this could be achieved by using binary option in R CMD build,
but in fact it packages source code that could be easily printed once the
library is loaded. Is there an option to avoid visibility of the source?
An
OK, gentlemen, i agree with you in general. I was not talking about a general
purpose, general use package that one prepares for CRAN. I am sure you are
familiar professionally or can imagine situations where you need to
demonstrate a solution to a specific task without fully disclosing the
details