[Rcpp-devel] Template instantiation of commonly-used types

that means this approach would not work? ___ Kevin Thornton Associate Professor Ecology and Evolutionary Biology University of California, Irvine http://www.molpopgen.org ___ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-

Re: [Rcpp-devel] Template instantiation of commonly-used types

I should clarify: those git gist are the "git clone" links. Here are the direct links for viewing: The .h: https://gist.github.com/molpopgen/5180d60689fa8d6cb353 The .cpp: https://gist.github.com/molpopgen/c13135659e0b27421a3a _______ Kevin Thornton Associate

Re: [Rcpp-devel] Template instantiation of commonly-used types

On Oct 15, 2014, at 11:01 AM, Dirk Eddelbuettel wrote: > > On 15 October 2014 at 10:28, Kevin Thornton wrote: > | I should clarify: those git gist are the "git clone" links. Here are the > direct links for viewing: > | > | The .h: https://gist.github.com/mo

Re: [Rcpp-devel] Template instantiation of commonly-used types

fortable moving away from header-only-ness > in Rcpp (although we could be persuaded otherwise) -- reducing compile > time / binary size doesn't seem a convincing enough reason to steer > away from being header only as possible. > > On Wed, Oct 15, 2014 at 11:01 AM, Dirk Eddel

Re: [Rcpp-devel] Template instantiation of commonly-used types

10:28, Kevin Thornton wrote: > | I should clarify: those git gist are the "git clone" links. Here are the > direct links for viewing: > | > | The .h: https://gist.github.com/molpopgen/5180d60689fa8d6cb353 > | > | The .cpp: https://gist.github.com/molpopgen/c13135659e0

Re: [Rcpp-devel] assert() for Rcpp?

gt; Cambridge MA 02138-2901 > > > lmirat...@stat.harvard.edu > 510-735-7635 > > > > > ___ > Rcpp-devel mailing list > Rcpp-devel@lists.r-forge.r-project.org > https://lists.r-forge.r-project.org/cgi-bi

Re: [Rcpp-devel] assert() for Rcpp?

l wrote: > > > On 18 February 2015 at 08:34, Kevin Thornton wrote: > | Isn't there a potential issue if a package depends on multiple header-only > C++ libraries, each of which may include ? You'd have multiple > definitions of the macro floating around, and the com

Re: [Rcpp-devel] assert() for Rcpp?

ote: > > > Hi Kevin, > > On 18 February 2015 at 09:02, Kevin Thornton wrote: > | Hi Dirk, > | > | Sorry, but your response is unclear to me. What was "taken care of"? What > is 'tinyformat'? Are you trying to say that this method of defining assert &g

Re: [Rcpp-devel] assert() for Rcpp?

Thanks--this helps. I have a project based on Rcpp and another header-only library where this could have been an issue. > On Feb 18, 2015, at 10:53 AM, Dirk Eddelbuettel wrote: > > > On 18 February 2015 at 09:31, Kevin Thornton wrote: > | Hi Dirk, > | > | Thanks. I

[Rcpp-devel] Problem with IntegerVector::value_type in recent Rcpp

p types? Best, Kevin _______ Kevin Thornton Associate Professor Ecology and Evolutionary Biology University of California, Irvine http://www.molpopgen.org http://github.com/molpopgen http://github.com/ThorntonLab ___ Rcpp-devel mailing list Rcpp

Re: [Rcpp-devel] Problem with IntegerVector::value_type in recent Rcpp

pp11/Rcpp14, VTYPE::value_type is defined like this: > > typedef typename traits::storage_type::type value_type ; > > so IntegerVector::value_type is int, and therefore you get what you > rightfully expect. > > > Romain > > >> Le 31 mars 2015 à 00:19,

[Rcpp-devel] Bizarre Rcpp::XPtr problem on GCC

Hi, I’m currently working on a header-only library that it intended to act as a “glue" layer between an existing C++11 library (also header only) and R, by means of Rcpp. Basically, I am trying to provide some generic templates that perform operations using the existing C++11 library and retur

Re: [Rcpp-devel] Bizarre Rcpp::XPtr problem on GCC

; > On 20 May 2015 at 15:22, Kevin Thornton wrote: > | Hi, > | > | I’m currently working on a header-only library that it intended to act as a > | “glue" layer between an existing C++11 library (also header only) and R, by > | means of Rcpp. > | > | Basically, I am tr

Re: [Rcpp-devel] Bizarre Rcpp::XPtr problem on GCC

w tuple_t(a,a)); } } SEXP foofunc_caller(const int & a) { return foo::foofunc(a); } > On May 20, 2015, at 5:50 PM, Hao Ye wrote: > > Kevin, > > I think Dirk is looking for a MWE (minimal working example). > > Best, > -- > Hao Ye > h...@ucsd.edu > >

Re: [Rcpp-devel] Bizarre Rcpp::XPtr problem on GCC

Dirk, OK, I’ll try again. I’ll respond out of order: c) There are no run instructions. This issue (as stated in all of my posts on this issue) is that GCC will not load the .so from the MWE because standard_delete_finalizer is missing. Compiling with clang++ does not have this issue, which

Re: [Rcpp-devel] correct way of making custom as and wrap functions available to other packages

A good guess is that the as/wrap definitions in wrappers.h are the culprit (https://github.com/dahtah/imager/blob/master/inst/include/wrappers.h ). Try declaring them as inline, or separating the definition from the declarati

Re: [Rcpp-devel] fatal error: 'omp.h' file not found

One may also use clang-omp from Homebrew if you wish to still use clang on OS X, but have OpenMP. --Kevin On Mon, Mar 14, 2016 at 9:31 AM Balamuta, James Joseph < balam...@illinois.edu> wrote: > Greetings and Salutations, > > > > OS X does not currently support OpenMP under the default compiler

Re: [Rcpp-devel] fatal error: 'omp.h' file not found

You should (read: I've not tested this myself...) be able to assign clang-omp and clang-omp++ to CC and CXX, respectively, in your ~/.R/Makevars file. On Mon, Mar 14, 2016 at 9:31 AM Balamuta, James Joseph < balam...@illinois.edu> wrote: > Greetings and Salutations, > > > > OS X does not currently

Re: [Rcpp-devel] advice on sharing C++ code across R and Python

es. > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > ___ > 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