Le 10/10/13 04:54, Dirk Eddelbuettel a écrit :
On 10 October 2013 at 04:02, Romain Francois wrote:
| Le 10/10/13 03:53, Dirk Eddelbuettel a écrit :
| > Ack. If the set of functions is small and rarely changes, then registration
| > using R's mechanism is indeed fine. Worked so far for getting J
On 10 October 2013 at 04:02, Romain Francois wrote:
| Le 10/10/13 03:53, Dirk Eddelbuettel a écrit :
| > Ack. If the set of functions is small and rarely changes, then registration
| > using R's mechanism is indeed fine. Worked so far for getting Jeff and
Josh's
| > xts into RcppXts, but that ha
Le 10/10/13 03:53, Dirk Eddelbuettel a écrit :
On 10 October 2013 at 03:29, Romain Francois wrote:
| Whoever who wants to use the classes it defines. dplyrRcpp exists mainly
| for facilitating the implementation of dplyr, but some of the concepts
| are general and could be used as building block
On 10 October 2013 at 03:29, Romain Francois wrote:
| Whoever who wants to use the classes it defines. dplyrRcpp exists mainly
| for facilitating the implementation of dplyr, but some of the concepts
| are general and could be used as building blocks of other things.
|
| I could/will make these
Le 10/10/13 03:21, Dirk Eddelbuettel a écrit :
On 10 October 2013 at 02:56, Romain Francois wrote:
| Le 10/10/13 02:41, Dirk Eddelbuettel a écrit :
| >
| > (Combining two of your emails)
| >
| > On 10 October 2013 at 01:08, Romain Francois wrote:
| > | RcppGSL does not export its LdFlags, if it
On 10 October 2013 at 02:56, Romain Francois wrote:
| Le 10/10/13 02:41, Dirk Eddelbuettel a écrit :
| >
| > (Combining two of your emails)
| >
| > On 10 October 2013 at 01:08, Romain Francois wrote:
| > | RcppGSL does not export its LdFlags, if it did, you'd see the warning
| > | when you load it
Le 10/10/13 02:41, Dirk Eddelbuettel a écrit :
(Combining two of your emails)
On 10 October 2013 at 01:08, Romain Francois wrote:
| RcppGSL does not export its LdFlags, if it did, you'd see the warning
| when you load it.
Good catch ... but turns out I don't (to my surprise).
Yes; My mistake
(Combining two of your emails)
On 10 October 2013 at 01:08, Romain Francois wrote:
| RcppGSL does not export its LdFlags, if it did, you'd see the warning
| when you load it.
Good catch ... but turns out I don't (to my surprise).
It seems to work. Maybe NAMESPACE really do help. Full log at b
Le 10/10/13 00:14, Dirk Eddelbuettel a écrit :
On 10 October 2013 at 00:05, Romain Francois wrote:
| That will then quickly become a mess. Having the convention
| package:::LdFlags() was fine.
I agree. It was a perfectly legit use of ::: but then the powers of CRAN do
other things do we don't a
Le 10/10/13 00:43, Dirk Eddelbuettel a écrit :
On 9 October 2013 at 17:14, Dirk Eddelbuettel wrote:
| The other immediate defensive way would be to use NAMESPACE etc on the client
| package and not load Rcpp and Rcpp$foo but just importFrom() etc what is
needed.
An 'Imports:' and NAMESPACE ent
Kevin,
On 9 October 2013 at 15:37, Kevin Ushey wrote:
| For what it's worth, this may be unnecessary for now. There are packages on
| CRAN that pass with no notes AFAICS, using Rcpp:::LdFlags in Makevars. Use of
| Rcpp:::LdFlags() within Makevars does not trigger any explicit notes for me in
| th
On 9 October 2013 at 17:14, Dirk Eddelbuettel wrote:
| The other immediate defensive way would be to use NAMESPACE etc on the client
| package and not load Rcpp and Rcpp$foo but just importFrom() etc what is
needed.
An 'Imports:' and NAMESPACE entry appears to be all it takes. RcppGSL also
has
Hi Dirk, Romain,
For what it's worth, this may be unnecessary for now. There are packages on
CRAN that pass with no notes AFAICS, using Rcpp:::LdFlags in Makevars. Use
of Rcpp:::LdFlags() within Makevars does not trigger any explicit notes for
me in the current R-devel on any of my packages, altho
On 10 October 2013 at 00:05, Romain Francois wrote:
| That will then quickly become a mess. Having the convention
| package:::LdFlags() was fine.
I agree. It was a perfectly legit use of ::: but then the powers of CRAN do
other things do we don't agree with but cannot easily alter.
| Or perhap
Le 09/10/13 23:43, Dirk Eddelbuettel a écrit :
On 9 October 2013 at 23:13, Romain Francois wrote:
| Le 09/10/13 03:41, Dirk Eddelbuettel a écrit :
| >
| > On 8 October 2013 at 16:53, Dirk Eddelbuettel wrote:
| > | | This is also what's done in e.g. Rcpp.package.skeleton. However,
following the
On 9 October 2013 at 23:13, Romain Francois wrote:
| Le 09/10/13 03:41, Dirk Eddelbuettel a écrit :
| >
| > On 8 October 2013 at 16:53, Dirk Eddelbuettel wrote:
| > | | This is also what's done in e.g. Rcpp.package.skeleton. However,
following the
| > | | new guidelines from CRAN, RcppLdFlags was
Le 09/10/13 03:41, Dirk Eddelbuettel a écrit :
On 8 October 2013 at 16:53, Dirk Eddelbuettel wrote:
| | This is also what's done in e.g. Rcpp.package.skeleton. However, following
the
| | new guidelines from CRAN, RcppLdFlags was exported, but not LdFlags. I
wonder
|
| Darn. Error on my part.
17 matches
Mail list logo
