[Rcpp-devel] RcppArmadillo pre-release at Github
Conrad aims to release Armadillo 4.100 next week. He suggested that I prepare a pre-release of RcppArmadillo based on the current snapshot. This is now in Github (https://github.com/RcppCore/RcppArmadillo). I started this off in a branch which I since merged as all tests passed fine. As this is not a major release, so we're not expecting breaking changes. It would be nice if those working with RcppArmadillo could update to the current Github version to test this pre-release in order to catch any odd surprises. Thanks, Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com ___ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
Re: [Rcpp-devel] Avoiding having to write .h files
Hi,
Then just put fun1 and fun2 in the same file. This is yet again less work than
having two files.
Romain
Le 25 févr. 2014 à 12:45, Søren Højsgaard a écrit :
> Only because it is extra work... Anyway, I hope this
> Rcpp::interfaces(r,cpp)-feature gets up and running again :)
>
> Søren
>
> -Original Message-
> From: Romain François [mailto:rom...@r-enthusiasts.com]
> Sent: 25. februar 2014 12:39
> To: Søren Højsgaard
> Cc: rcpp-devel@lists.r-forge.r-project.org (rcpp-de...@r-forge.wu-wien.ac.at)
> Subject: Re: [Rcpp-devel] Avoiding having to write .h files
>
> Hello,
>
> Why do you want to avoid writing headers. I guess you could use extern
>
> For example, in foo1.cpp :
>
> double fun1(){
> return 2.0 ;
> }
>
> In foo2.cpp ;
>
> extern double fun1() ;
>
> double fun2(){
> return fun1() + 2;
> }
>
> Romain
>
> Le 25 févr. 2014 à 12:28, Søren Højsgaard a écrit :
>
>> Dear all,
>>
>> If in a package I have foo1.cpp with function fun1 and foo2.cpp with fun2
>> (which uses fun1 from foo1.cpp) then I must write foo1.h and include in
>> foo2.cpp. Right? Is there another approach so that I do not have to write
>> these header files?
>>
>> Using Rcpp::interfaces(r,cpp) should take care of that (according to the
>> Rcpp-attributes vignette, at least that is my understanding) but I have seen
>> on the list that there is a bug in this feature with the current Rcpp
>> version (and also with the devel version on github).
>>
>> Cheers
>> Søren
>
___
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
Re: [Rcpp-devel] Avoiding having to write .h files
Only because it is extra work... Anyway, I hope this
Rcpp::interfaces(r,cpp)-feature gets up and running again :)
Søren
-Original Message-
From: Romain François [mailto:rom...@r-enthusiasts.com]
Sent: 25. februar 2014 12:39
To: Søren Højsgaard
Cc: rcpp-devel@lists.r-forge.r-project.org (rcpp-de...@r-forge.wu-wien.ac.at)
Subject: Re: [Rcpp-devel] Avoiding having to write .h files
Hello,
Why do you want to avoid writing headers. I guess you could use extern
For example, in foo1.cpp :
double fun1(){
return 2.0 ;
}
In foo2.cpp ;
extern double fun1() ;
double fun2(){
return fun1() + 2;
}
Romain
Le 25 févr. 2014 à 12:28, Søren Højsgaard a écrit :
> Dear all,
>
> If in a package I have foo1.cpp with function fun1 and foo2.cpp with fun2
> (which uses fun1 from foo1.cpp) then I must write foo1.h and include in
> foo2.cpp. Right? Is there another approach so that I do not have to write
> these header files?
>
> Using Rcpp::interfaces(r,cpp) should take care of that (according to the
> Rcpp-attributes vignette, at least that is my understanding) but I have seen
> on the list that there is a bug in this feature with the current Rcpp version
> (and also with the devel version on github).
>
> Cheers
> Søren
___
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
Re: [Rcpp-devel] Avoiding having to write .h files
Hello,
Why do you want to avoid writing headers. I guess you could use extern
For example, in foo1.cpp :
double fun1(){
return 2.0 ;
}
In foo2.cpp ;
extern double fun1() ;
double fun2(){
return fun1() + 2;
}
Romain
Le 25 févr. 2014 à 12:28, Søren Højsgaard a écrit :
> Dear all,
>
> If in a package I have foo1.cpp with function fun1 and foo2.cpp with fun2
> (which uses fun1 from foo1.cpp) then I must write foo1.h and include in
> foo2.cpp. Right? Is there another approach so that I do not have to write
> these header files?
>
> Using Rcpp::interfaces(r,cpp) should take care of that (according to the
> Rcpp-attributes vignette, at least that is my understanding) but I have seen
> on the list that there is a bug in this feature with the current Rcpp version
> (and also with the devel version on github).
>
> Cheers
> Søren
___
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
[Rcpp-devel] Avoiding having to write .h files
Dear all, If in a package I have foo1.cpp with function fun1 and foo2.cpp with fun2 (which uses fun1 from foo1.cpp) then I must write foo1.h and include in foo2.cpp. Right? Is there another approach so that I do not have to write these header files? Using Rcpp::interfaces(r,cpp) should take care of that (according to the Rcpp-attributes vignette, at least that is my understanding) but I have seen on the list that there is a bug in this feature with the current Rcpp version (and also with the devel version on github). Cheers Søren ___ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
