Message-ID: <CALEXWq0Kt6gkceNwzAo4oFWAbuNZ1x2VZw=tgZ7i8Sb_HizEiA@mail.gmail.com>
Date: 2017-07-29T14:25:47Z
From: Iñaki Ucar
Subject: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)
In-Reply-To: <22908.39043.167711.463011@bud.eddelbuettel.com>
2017-07-29 16:15 GMT+02:00 Dirk Eddelbuettel <edd at debian.org>:
>
> On 29 July 2017 at 15:48, I?aki ?car wrote:
> | Yes, I am, and I think that my use case is slightly different. My
> | understanding is, correct me if I'm wrong, that RcppDE implements some
> | C++ functions and the user is able to choose which one the backend
> | should use via its name. In my case, the user is the one that would
> | implement a C++ function for which the backend is unaware: it doesn't
> | know the name and it's located in another dynamic library.
>
> Exactly the same here. You misunderstood the example and failed to grasp the
> generality.
>
> All you do is specify a signature -- i.e. accepting two NumericVector and
> returning a third. Then the external pointer takes care of everything. You
> as the API provider known nothing about the supplied functions.
>
> Ditto in RcppDE. Optmises any function.
Ok, then I have to check RcppDE more in detail. Thanks for your help!
I?aki