[Rcpp-devel] RcppArmadillo pre-release at Github

2014-02-25 Thread Dirk Eddelbuettel
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

Re: [Rcpp-devel] Avoiding having to write .h files

2014-02-25 Thread Romain François
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 >

Re: [Rcpp-devel] Avoiding having to write .h files

2014-02-25 Thread Søren Højsgaard
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:[email protected]] Sent: 25. februar 2014 12:39 To: Søren Højsgaard Cc: [email protected]

Re: [Rcpp-devel] Avoiding having to write .h files

2014-02-25 Thread Romain François
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, >

[Rcpp-devel] Avoiding having to write .h files

2014-02-25 Thread Søren Højsgaard
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 ca