Le 31/05/10 20:07, Romain Francois a écrit :
Thanks John,
Le 31/05/10 18:23, John Chambers a écrit :
Just a couple of comments.
1. class names
One result of creating an S4 class with the same name as the C++ class
is that you may be hiding another S4 class of that name. Always possible
in any
Thanks John,
Le 31/05/10 18:23, John Chambers a écrit :
Just a couple of comments.
1. class names
One result of creating an S4 class with the same name as the C++ class
is that you may be hiding another S4 class of that name. Always possible
in any application, but when dealing with an inter-sy
Le 29/05/10 09:10, Romain Francois a écrit :
Hello,
Currently, when exposing a c++ class to R through a Rcpp module, e.g:
class World {
public:
World() : msg("hello"){}
void set(std::string msg) { this->msg = msg; }
std::string greet() { return msg; }
private:
std::string msg;
};
void clearW
Hello,
Currently, when exposing a c++ class to R through a Rcpp module, e.g:
class World {
public:
World() : msg("hello"){}
void set(std::string msg) { this->msg = msg; }
std::string greet() { return msg; }
private:
std::string msg;
};
void clearWorld( World* w){
w->set
