[Rcpp-devel] Local .h files and Rcpp attributes

[JJ Allaire]

For it to actually work though we'd need to modify Makevars as well (as
Romain pointed out) so that the RcppExports.cpp could see the include file.
This might get trickly. My thought was that we should either generate a
fully working solution or failing that generation enough
pointers/documentation to get most users over the hump.

J


On Sat, Oct 19, 2013 at 3:56 PM, Dirk Eddelbuettel <edd at debian.org> wrote:

>
> On 19 October 2013 at 15:40, JJ Allaire wrote:
> |
> |     Maybe you could follow the example of Rcpp.package.skeleton() and
> just drop
> |     an empty yet amply commented file there?  By "being there" users
> have a
> |     better chance of stumbling over it :)
> |
> |
> | Since this would involve creating a new directory (inst/include) perhaps
> I
> | could instead emit comments at the top of RcppExports.cpp explaining the
> | mechanism?
>
> True, but maybe I'd still go for it.  inst/include/ is after all the place
> via which a any package foo can provide its headers to another package bar
> which simply adds 'LinkingTo: foo'.
>
> Currently, the 'cost' of attributes is one extra RcppExports.R, one
> RcppExports.cpp and we'd add a new (small, few lines with comments) header
> file in a new directory.  Seems fair to me -- but entirely your call.
>
> Restraint in not cluttering user systems is also a good thing. We'd be back
> to the need for more/better documentation though.
>
> Dirk
>
> --
> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20131019/45346662/attachment.html>