> I've just commited some code that will help us identify if a given R object
> (a SEXP) can be seen as a given c++ type (e.g. IntegerVector, etc ...)
>
> Works like this:
>
> SEXP x ; // a SEXP from somewhere, or an RObject
> is( x ) ;
> is( x ) ;
> is( x ) ;
Nice!
Combining this with attribute
Le 17 juil. 2013 à 14:10, JJ Allaire a écrit :
>> But maybe it is not worth the trouble. Maybe this is simply a documentation
>> issue on hiw to dispatch.
>
> Yes, I think creating an automatic dispatch system that's general enough to
> matter might not be worth the effort. Documentation + so
>
> But maybe it is not worth the trouble. Maybe this is simply a
> documentation issue on hiw to dispatch.
>
Yes, I think creating an automatic dispatch system that's general enough to
matter might not be worth the effort. Documentation + some supporting
utilities is probably the optimal path.
__
Le 17 juil. 2013 à 13:41, JJ Allaire a écrit :
>> dispatching could also happen in attributes. Why not having something like
>> this:
>>
>> // [[Rcpp::export]]
>> void foo( NumericVector x) {
>> // do some stuff
>> }
>>
>> // [[Rcpp::export]]
>> void foo( IntegerVector x) {
>> // do so
>
> dispatching could also happen in attributes. Why not having something like
> this:
>
> // [[Rcpp::export]]
> void foo( NumericVector x) {
> // do some stuff
> }
>
> // [[Rcpp::export]]
> void foo( IntegerVector x) {
> // do some other stuff
> }
>
> This would involve some work in the wa
