[Rcpp-devel] Accessing an attribute object in C/C++

2012-07-11 Thread Silkworth,David J.
I have built the following example in order to demonstrate my concern. In reality I am obtaining an object such as the example mymat with an attached vector as an attribute from Douglas Bates' 1998 C code for spline_basis in the splines package. It seems that back in the days of stone knives a

Re: [Rcpp-devel] RcppArmadillo installation issue

2012-07-11 Thread c s
On Wed, Jul 11, 2012 at 5:03 AM, Vinh Nguyen wrote: >> That said, it very much looks like an issue with g++ 4.7.*. I actually made a >> small change to make it work at my end (Debian testing, g++-4.7.1). >> > > Yes, g++ 4.7.* was used... GCC versions 4.7.0 and 4.7.1 are full of bugs within the C+

Re: [Rcpp-devel] link issue when Rcpp package is installed in a path with space

2012-07-11 Thread Dirk Eddelbuettel
On 11 July 2012 at 20:18, Jiqiang Guo wrote: | Dear List, | | From some reason, my Rcpp package on windows is installed in C:/Program Files/ Not "some reason" but the [badly chosen] default of the R Windows Installer. The R-on-Windows FAQ, as I recall, recommends NOT to install in a path with s

Re: [Rcpp-devel] Bug: RcppArmadillo.package.skeleton builds faulty man/*.Rd files

2012-07-11 Thread Dirk Eddelbuettel
Nathan, Two more comments. First, I am not sure you can even do what you did. When I call Rcpp.armadillo.package() as (where I omit the R file argument -- no point including a file loading inline in a package, or redefining these functions) RcppArmadillo.package.skeleton(name='inlineExample'

[Rcpp-devel] link issue when Rcpp package is installed in a path with space

2012-07-11 Thread Jiqiang Guo
Dear List, >From some reason, my Rcpp package on windows is installed in C:/Program Files/R/R-2.15.1/library/, which has a space in the path. So in the end, when compiling cpp code using inline package, I would have the following error, which prevent me using Rcpp at all. Compilation argument:

Re: [Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Dirk Eddelbuettel
On 11 July 2012 at 18:52, Bob Carpenter wrote: | On 7/11/12 6:24 PM, Dirk Eddelbuettel wrote: | > Is there a reason this is off list? Can we please move it back? | | No reason --- it's just that the Rcpp list is the only | list I use where "reply" doesn't go back to the | list, so I keep mistaken

Re: [Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Bob Carpenter
On 7/11/12 6:24 PM, Dirk Eddelbuettel wrote: Is there a reason this is off list? Can we please move it back? No reason --- it's just that the Rcpp list is the only list I use where "reply" doesn't go back to the list, so I keep mistakenly replying only to Dirk. I have an actual response inline

Re: [Rcpp-devel] Bug: RcppArmadillo.package.skeleton builds faulty man/*.Rd files

2012-07-11 Thread Dirk Eddelbuettel
Hi Nathan, On 11 July 2012 at 17:07, Nathan VanHoudnos wrote: | Hi all, | | Is the appropriate place to report bugs, or should I send this somewhere else? Sure is. | I'm using:  | | Package: RcppArmadillo | Version: 0.3.2.3 | Date: $Date: 2012-06-29 20:51:46 -0500 (Fri, 29 Jun 20

[Rcpp-devel] Bug: RcppArmadillo.package.skeleton builds faulty man/*.Rd files

2012-07-11 Thread Nathan VanHoudnos
Hi all, Is the appropriate place to report bugs, or should I send this somewhere else? I'm using: Package: RcppArmadillo Version: 0.3.2.3 Date: $Date: 2012-06-29 20:51:46 -0500 (Fri, 29 Jun 2012) $ Minimal example: # # File : build-R-pacakge.R # ##

Re: [Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Dirk Eddelbuettel
Further follow-up, quoting from 'Writing R Extensions': - 1.7 Writing portable packages = [...] * Do be very careful with passing arguments between R, C and FORTRAN code. In particula

Re: [Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Dirk Eddelbuettel
On 11 July 2012 at 16:46, Walter Mascarenhas wrote: | Sorry if this sounds too naive (I now little about R,), | but what is wrong with using the types | |   uint64_t, int64_t etc  | | which are defined in the c++ standard header ? I like those too --- but on _32 bit Windows_ they turn into (or

Re: [Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Walter Mascarenhas
Sorry if this sounds too naive (I now little about R,), but what is wrong with using the types uint64_t, int64_t etc which are defined in the c++ standard header ? walter. On Wed, Jul 11, 2012 at 4:34 PM, Bob Carpenter wrote: > Jiqiang created a standalone example that illustrate

[Rcpp-devel] 64-bit ints on Windows 64-bit via size_t, unsigned long long, or unsigned __int64

2012-07-11 Thread Bob Carpenter
Jiqiang created a standalone example that illustrates our problem with wrapping size_t into Rcpp on Win64. The simple example is as follows (full running dump from R/Rcpp below): size_t b = 100; Rcpp::List lst(a); lst["b"] = b; return lst; We found this discussion: http://stackoverf