>
> 2. If my package already has a namespace named ernm, is an extra one
> wrapped around it, so that extending packages would have to use
> ernm::ernm::bar()?
>
No, the generated header file for a package exports functions within the
package namespace but that doesn't preclude other headers from
Le 15/11/12 01:02, Darren Cook a écrit :
so when the object returns from this as, a copy is involved. We return a
T, not a T*, or a T&
I wonder if this gets optimized away, though? E.g.
http://blog.knatten.org/2011/08/26/dont-be-afraid-of-returning-by-value-know-the-return-value-optimization/
> so when the object returns from this as, a copy is involved. We return a
> T, not a T*, or a T&
I wonder if this gets optimized away, though? E.g.
http://blog.knatten.org/2011/08/26/dont-be-afraid-of-returning-by-value-know-the-return-value-optimization/
Definitely worth profiling and/or looki
Le 15/11/12 00:14, Richard Downe a écrit :
Thanks. I had recently been playing with using XPtr to do some of the
passing RcppModule objects back into c++, with only limited success, so
this will be a welcome change.
Also, I can probably finally cull my hackery of calling
Rcpp::internal::make_ne
Thanks. I had recently been playing with using XPtr to do some of the
passing RcppModule objects back into c++, with only limited success, so
this will be a welcome change.
Also, I can probably finally cull my hackery of calling
Rcpp::internal::make_new_object in my factory methods, which alw
On 14 November 2012 at 13:46, Ian Fellows wrote:
|
| So,… um… Wow!
|
| This is some pretty incredible work, and lines up almost to the letter with
the real world issues that I was experiencing with my package. Reading over the
vignette, a couple of questions popped into my head.
Thanks :) We'
Le 14/11/12 22:46, Ian Fellows a écrit :
So,… um… Wow!
:-)
This is some pretty incredible work, and lines up almost to the letter with the
real world issues that I was experiencing with my package. Reading over the
vignette, a couple of questions popped into my head.
With the //Rcpp::inte
So,… um… Wow!
This is some pretty incredible work, and lines up almost to the letter with the
real world issues that I was experiencing with my package. Reading over the
vignette, a couple of questions popped into my head.
With the //Rcpp::interfaces(cpp) declaration
1. Are classes also export
