Skip to content

[Rcpp-devel] Wrapping copy constructor in rcpp?

4 messages · Tama Ma, Dirk Eddelbuettel

#
Dear Rcpp developers,

	Maybe my previous email has been ignored. I am asking whether there is a possibility to wrap the copy constructor in a C++ class via Rcpp? 

	Thank you very much.

Best regards,
Tama Ma 
(+41 78 640 50 15)

pingnang at phys.ethz.ch
www.phys.ethz.ch/~pingnang

HIT K 31.3
Institut f?r Theoretische Physik
Wolfgang-Pauli-Strasse 27
ETH H?nggerberg
8093 Z?rich
Switzerland
#
On 4 November 2011 at 16:08, Tama Ma wrote:
| Dear Rcpp developers,
| 
| 	Maybe my previous email has been ignored. I am asking whether there is a possibility to wrap the copy constructor in a C++ class via Rcpp? 

You get a firm "maybe" and even an additional "why not" from me.

I am a little unsure exactly what you are after.  Basic Rcpp functions _all_
have to conform to the .Call()-required interface

     extern "C" SEXP foo(SEXP a, SEXP b)

signature (for a variable number of arguments). 

So no ctor or copy ctor here.  

So I presume you are talking about Rcpp Modules?  We have some documentation
on what is possible. If you don't see an explicit mention or example or unit
test doing it, then maybe it hasn't been implemented yet.  But this is Open
Source and you have already contributed a patch so you know the drill, right :)

Dirk
#
Dear Dirk,

	Thanks for the reply. I am pretty sure that it has not been implemented yet, and I will try to look into it. From a practical point of view, I would want to copy a "Rcpp" object in the R interface, and not a "copy-by-pointer" approach now. 
	Thank you once again.

Best regards,
Tama Ma
On Nov 4, 2011, at 4:48 PM, Dirk Eddelbuettel wrote:

            
Best regards,
Tama Ma 
(+41 78 640 50 15)

pingnang at phys.ethz.ch
www.phys.ethz.ch/~pingnang

HIT K 31.3
Institut f?r Theoretische Physik
Wolfgang-Pauli-Strasse 27
ETH H?nggerberg
8093 Z?rich
Switzerland
#
On 4 November 2011 at 17:08, Tama Ma wrote:
| Dear Dirk,
| 
| 	Thanks for the reply. I am pretty sure that it has not been implemented yet, and I will try to look into it. From a practical point of view, I would want to copy a "Rcpp" object in the R interface, and not a "copy-by-pointer" approach now. 

You mean just like what clone() does?

Dirk

| 	Thank you once again.
| 
| Best regards,
| Tama Ma
| 
|
| On Nov 4, 2011, at 4:48 PM, Dirk Eddelbuettel wrote:
| 
| >
| > On 4 November 2011 at 16:08, Tama Ma wrote:
| > | Dear Rcpp developers,
| > | 
| > | 	Maybe my previous email has been ignored. I am asking whether there is a possibility to wrap the copy constructor in a C++ class via Rcpp? 
| > 
| > You get a firm "maybe" and even an additional "why not" from me.
| > 
| > I am a little unsure exactly what you are after.  Basic Rcpp functions _all_
| > have to conform to the .Call()-required interface
| > 
| >     extern "C" SEXP foo(SEXP a, SEXP b)
| > 
| > signature (for a variable number of arguments). 
| > 
| > So no ctor or copy ctor here.  
| > 
| > So I presume you are talking about Rcpp Modules?  We have some documentation
| > on what is possible. If you don't see an explicit mention or example or unit
| > test doing it, then maybe it hasn't been implemented yet.  But this is Open
| > Source and you have already contributed a patch so you know the drill, right :)
| > 
| > Dirk
| > 
| > -- 
| > "Outside of a dog, a book is a man's best friend. Inside of a dog, it is too
| > dark to read." -- Groucho Marx
| > 
| 
| 
| Best regards,
| Tama Ma 
| (+41 78 640 50 15)
| 
| pingnang at phys.ethz.ch
| www.phys.ethz.ch/~pingnang
| 
| HIT K 31.3
| Institut f?r Theoretische Physik
| Wolfgang-Pauli-Strasse 27
| ETH H?nggerberg
| 8093 Z?rich
| Switzerland
|