On 13 September 2012 at 08:24, Darren Cook wrote:
| > You didn't show the 10 lines. I've looked these over
| > many times, but I didn't get it until just now. If anybody
| > else cares, here are the 3 that really matter...
| >
| > PREFIX/lib64/R/library/Rcpp/include/Rcpp/stats/norm.h
| > 106:RC
> You didn't show the 10 lines. I've looked these over
> many times, but I didn't get it until just now. If anybody
> else cares, here are the 3 that really matter...
>
> PREFIX/lib64/R/library/Rcpp/include/Rcpp/stats/norm.h
> 106:RCPP_DPQ_0(norm, Rcpp::stats::dnorm_0, Rcpp::stats::pnorm_0,
> Rc
On 12/09/12 06:56, Christian Gunning wrote:
On Tue, Sep 11, 2012 at 3:00 AM,
wrote:
It seems to be the casethat when the memory issue occurs, garbage
collection has just been called by R, at least according to gcinfo.In
particular, it is called when bar is called and cleans up the arguments
tha
On 12 September 2012 at 09:28, Rodney Sparapani wrote:
| On 09/12/2012 08:58 AM, Dirk Eddelbuettel wrote:
|
| > edd@max:~$ grep -r qnorm /usr/local/lib/R/site-library/Rcpp/include/ |
wc -l
| > 10
| > edd@max:~$
| >
| > There is no magic pixie dust. Some headers are script-generated,
On 12 September 2012 at 19:44, Umesh Chitre wrote:
| I have created a custom package with following steps:
|
| 1. Created a new package using Rcpp.package.skeleton(, module=TRUE)
| 2. Built using R CMD build
Please send __complete constructions__. It is not clear what you ran here
but I believe
On 09/12/2012 08:58 AM, Dirk Eddelbuettel wrote:
edd@max:~$ grep -r qnorm /usr/local/lib/R/site-library/Rcpp/include/ | wc -l
10
edd@max:~$
There is no magic pixie dust. Some headers are script-generated, even those
scripts are in SVN. Some of the p/q/d/r-sugar functions are from m
I have created a custom package with following steps:
1. Created a new package using Rcpp.package.skeleton(, module=TRUE)
2. Built using R CMD build
3. Loaded the pkg through the zip file created by build process
Now, when I try to invoke the rcpp_hello_world() method at R prompt, it throws
an e
On 12 September 2012 at 08:38, Rodney Sparapani wrote:
| On 09/07/2012 12:19 PM, Dirk Eddelbuettel wrote:
| > |> As a general, looking at the unit test files can be helpful. Here is
one for qnorm:
| > |>
| > |> "runit_qnorm_prob" = list(
| > |> signature( x = "numeric" ),
| > |> '
|
On 09/07/2012 12:19 PM, Dirk Eddelbuettel wrote:
|> As a general, looking at the unit test files can be helpful. Here is one
for qnorm:
|>
|> "runit_qnorm_prob" = list(
|> signature( x = "numeric" ),
|> '
|> NumericVector xx(x) ;
|> return List::create(_["lower"] = qnorm( xx
On 09/11/2012 10:29 AM, Ian Fellows wrote:
It sounds like you are actually stuck on step 2. Your statet R configuration is
not set up. In External Tools, go to R Config and make sure that you have all
your paths set up (e.g. R_HOME).
This is not an Rcpp issue in particular.
ian
Dear Ian:
On 12 September 2012 at 04:58, Christian Gunning wrote:
| >I understand that I cannot use Visual Studio compiler to build code written
in C++ that uses Rcpp header files. Assuming this is the >case, what are the
other options that I have to be able to code in C++ which either internally
uses Rc
>I understand that I cannot use Visual Studio compiler to build code written in
>C++ that uses Rcpp header files. Assuming this is the >case, what are the
>other options that I have to be able to code in C++ which either internally
>uses Rcpp sugar for R functionality or >implements its own meth
I understand that I cannot use Visual Studio compiler to build code written in
C++ that uses Rcpp header files. Assuming this is the case, what are the other
options that I have to be able to code in C++ which either internally uses Rcpp
sugar for R functionality or implements its own methods to
13 matches
Mail list logo
