Re: [Rcpp-devel] Question regarding integrating preexisting C++ code via Rcpp

2011-10-11 Thread Darren Cook
> My apologies for not posting comprehensive code. My intention was only to > lessen the reading burden for you. Don't post comprehensive code :-) But if you can discover the smallest possible example that shows the problem, that will encourage lots of helpful responses. > I am currently getting

Re: [Rcpp-devel] Question regarding integrating preexisting C++ code via Rcpp

2011-10-11 Thread Simon Fuller
Hello, My apologies for not posting comprehensive code. My intention was only to lessen the reading burden for you. However I must aver, despite your concerns to the contrary, taht you have already been very helpful. I have taken your advice on board, in particular concerning include order. I hav

Re: [Rcpp-devel] Question regarding integrating preexisting C++ code via Rcpp

2011-10-11 Thread Dirk Eddelbuettel
On 11 October 2011 at 10:53, Simon Fuller wrote: | To be safe, I wrote a couple of quick codes that use the relevant includes, and | these work fine when using g++ from the terminal, so I do not think that it is | my c++ sources as such that are causing the problem, as far as I can ascertain | my

Re: [Rcpp-devel] Question regarding integrating preexisting C++ code via Rcpp

2011-10-11 Thread Simon Fuller
Hello, I have run a couple more tests. I commented out: #include I then got the same error for #include , i.e: In file included from /usr/include/c++/4.5/queue:65:0, from /home/simon/College/PackageOne/src/BZip/BZip.h:11, from file21028e73.cpp:37: /usr/includ

Re: [Rcpp-devel] Question regarding integrating preexisting C++ code via Rcpp

2011-10-11 Thread Simon Fuller
Hello Davor, Yes, I think - I have: #ifndef HEADERNAME_IN_CAPS #define HEADERNAME_IN_CAPS 1 (..code..) #endif for all my headers. As far as I can tell the problem arises when fstream includes codecvt.h, which calls, on line 42: _GLIBCXX_BEGIN_NAMESPACE(std) I don't think this pertains to my own