Hi Charles,
I understand this is frustrating for you but we are wasting everybody's time
here. Can you please prepare a minimally reproducible example?
Also, maybe try some bisection. Does the problem go away after you remove
bigmemory/bigalgebra?
Dirk
--
http://dirk.eddelbuettel.com | @edde
Adding the #ifdef test removes the error with INT but I don't follow if you
are suggesting something else for the #ifdef test? I sadly continue to see
the same "length" errors once I fix the INT error in the BigMatrix.h file.
Current headers:
#ifdef REFBLAS
#include "refblas64longlong.h"
#define
On 24 February 2015 at 15:06, Charles Determan Jr wrote:
| Unfortunately I get the same errors with #include last as
| well as #include "bigmemory/BigMatrix.h" next to last. The latter results in
| additional errors in BigMatrix.h with the expansion of INT. Both scenarios
| still have "length p
Unfortunately I get the same errors with #include last as
well as #include "bigmemory/BigMatrix.h" next to last. The latter results
in additional errors in BigMatrix.h with the expansion of INT. Both
scenarios still have "length passed 4 arguments" errors.
On Tue, Feb 24, 2015 at 2:51 PM, Dirk
On 24 February 2015 at 14:41, Charles Determan Jr wrote:
| Thank you for that clarification, I always seem to forget that Rcpp packages
| have many libraries loaded by default. I have trimmed the headers down to the
| following to just
|
| #include
|
| However, some further background, I am w
Thank you for that clarification, I always seem to forget that Rcpp
packages have many libraries loaded by default. I have trimmed the headers
down to the following to just
#include
However, some further background, I am working on extending the bigalgebra
package (hence the interest in RcppArm
Do you really need the macros like GET_LENGTH that are defined in
#include
? It looks like they are meant to ease porting of C code written for S or
S+,
but very little code these days is written for S or S+ and certainly not
Rcpp
code.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Tue, Fe
On 24 February 2015 at 12:30, Charles Determan Jr wrote:
| Greetings,
|
| I have run in to an error when compiling an R package that has the following
| headers in the only cpp file at the moment:
|
| #include
| #include
| #include
|
| #define R_NO_REMAP
|
| #include
| #include
| #include
On 24 February 2015 at 15:45, Miratrix, Luke wrote:
| As an inexperienced person myself, I was trying to wrap a C++ stand-alone
| package so it could be called from R and was trying to preserve some of
| the safety features and error-checking. My understanding of asserts is
| they are to catch di
Greetings,
I have run in to an error when compiling an R package that has the
following headers in the only cpp file at the moment:
#include
#include
#include
#define R_NO_REMAP
#include
#include
#include
Now, I am also trying to use RcppArmadillo with:
#include
// [[Rcpp::depends(Rcpp
On Tue, Feb 24, 2015 at 10:59 AM, Tim Keitt wrote:
>
>
> On Tue, Feb 24, 2015 at 9:45 AM, Miratrix, Luke > wrote:
>
>>
>> As an inexperienced person myself, I was trying to wrap a C++ stand-alone
>> package so it could be called from R and was trying to preserve some of
>> the safety features an
On Tue, Feb 24, 2015 at 9:45 AM, Miratrix, Luke
wrote:
>
> As an inexperienced person myself, I was trying to wrap a C++ stand-alone
> package so it could be called from R and was trying to preserve some of
> the safety features and error-checking. My understanding of asserts is
> they are to ca
As an inexperienced person myself, I was trying to wrap a C++ stand-alone
package so it could be called from R and was trying to preserve some of
the safety features and error-checking. My understanding of asserts is
they are to catch disasters that indicate bugs in the code itself, and are
thus
13 matches
Mail list logo
