On 6 June 2013 at 13:17, Dirk Eddelbuettel wrote:
|
| On 6 June 2013 at 19:05, Simon Zehnder wrote:
| | sorry I had overseen this message from you. Okay, so the explicit cast to
SEXP together with the assignment operator makes the deal. But it still
includes the reuse of memory right, i.e. the
On 6 June 2013 at 19:05, Simon Zehnder wrote:
| sorry I had overseen this message from you. Okay, so the explicit cast to
SEXP together with the assignment operator makes the deal. But it still
includes the reuse of memory right, i.e. the '=' does not call the copy
constructor?
But how could
Le 06/06/13 19:05, Simon Zehnder a écrit :
Hi Romain,
sorry I had overseen this message from you. Okay, so the explicit cast to SEXP
together with the assignment operator makes the deal. But it still includes the
reuse of memory right, i.e. the '=' does not call the copy constructor?
Yep. No
Hi Romain,
sorry I had overseen this message from you. Okay, so the explicit cast to SEXP
together with the assignment operator makes the deal. But it still includes the
reuse of memory right, i.e. the '=' does not call the copy constructor?
Further, this only solves the ambiguity for the conv
Hi Romain,
oh thanks! I haven't recognized this one, even though I use armadillo now for
more than a half year ;)
best
Simon
On Jun 6, 2013, at 6:48 PM, Romain Francois wrote:
> Le 06/06/13 18:38, Simon Zehnder a écrit :
>> Hi Dirk,
>>
>> thanks for the fast reply. It seems, that using in
Hi Simon,
On 6 June 2013 at 18:38, Simon Zehnder wrote:
| thanks for the fast reply. It seems, that using ints is the only possibility
here. I understand though, that the arma::umat has type 'unsigned int', hasn't
it? So in this case I wouldn't be able to use umat, but rather mat, right?
Yes,
Le 06/06/13 18:38, Simon Zehnder a écrit :
Hi Dirk,
thanks for the fast reply. It seems, that using ints is the only possibility here. I
understand though, that the arma::umat has type 'unsigned int', hasn't it? So in this
case I wouldn't be able to use umat, but rather mat, right?
Which is
Hi Dirk,
thanks for the fast reply. It seems, that using ints is the only possibility
here. I understand though, that the arma::umat has type 'unsigned int', hasn't
it? So in this case I wouldn't be able to use umat, but rather mat, right?
Best
Simon
On Jun 6, 2013, at 6:32 PM, Dirk Eddelbue
Le 06/06/13 18:03, Simon Zehnder a écrit :
Hi Rcpp:Users, and Rcpp::Devels,
I encountered the following problem when working today/yesterday on my project:
1. In R create an S4-object with the following slot:
setClass("myclass", representation(S = "array"))
mclass <- new("myclass", S = array(
On 6 June 2013 at 18:03, Simon Zehnder wrote:
| What I need is an arma::umat in C++ and if possible in addition an integer
array in R. Is this possible?
R itself has no unsigned integers (just as it has no [signed or unsigned] short
or long integeger).
You should be able to write wrappers thou
Hi Rcpp:Users, and Rcpp::Devels,
I encountered the following problem when working today/yesterday on my project:
1. In R create an S4-object with the following slot:
setClass("myclass", representation(S = "array"))
mclass <- new("myclass", S = array(0, dim = c(100, 10)))
2. In C++ compile a fu
11 matches
Mail list logo
