[Rd] predict.loess() segfaults for large n?

2013-03-01 Thread Hiroyuki Kawakatsu
Hi, I am segfaulting when using predict.loess() (checked with r62092). I've traced the source with the help of valgrind (output pasted below) and it appears that this is due to int overflow when allocating an int work array in loess_workspace(): liv = 50 + ((int)pow((double)2, (double)D) + 4)

Re: [Rd] conflict between rJava and data.table

2013-03-01 Thread Matthew Dowle
Simon Urbanek wrote : Can you elaborate on the details as of where this will be a problem? Packages should not be affected since they should be importing the namespaces from the packages they use, so the only problem would be in a package that uses both data.table and rJava -- and this is eas

Re: [Rd] conflict between rJava and data.table

2013-03-01 Thread Simon Urbanek
On Mar 1, 2013, at 8:03 AM, Matthew Dowle wrote: > > Simon Urbanek wrote : >> Can you elaborate on the details as of where this will be a problem? Packages >> should not be affected since they should be importing the namespaces from the >> packages they use, so the only problem would be in a pack

Re: [Rd] conflict between rJava and data.table

2013-03-01 Thread Matthew Dowle
On 01.03.2013 16:13, Simon Urbanek wrote: On Mar 1, 2013, at 8:03 AM, Matthew Dowle wrote: Simon Urbanek wrote : Can you elaborate on the details as of where this will be a problem? Packages should not be affected since they should be importing the namespaces from the packages they use, so t

Re: [Rd] conflict between rJava and data.table

2013-03-01 Thread Simon Urbanek
On Mar 1, 2013, at 11:40 AM, Matthew Dowle wrote: > On 01.03.2013 16:13, Simon Urbanek wrote: >> On Mar 1, 2013, at 8:03 AM, Matthew Dowle wrote: >> >>> >>> Simon Urbanek wrote : Can you elaborate on the details as of where this will be a problem? Packages should not be affected

Re: [Rd] conflict between rJava and data.table

2013-03-01 Thread Matthew Dowle
On 01.03.2013 20:19, Simon Urbanek wrote: On Mar 1, 2013, at 11:40 AM, Matthew Dowle wrote: On 01.03.2013 16:13, Simon Urbanek wrote: On Mar 1, 2013, at 8:03 AM, Matthew Dowle wrote: Simon Urbanek wrote : Can you elaborate on the details as of where this will be a problem? Packages should

[Rd] .Call interface: Use R SEXP as C mutable *char

2013-03-01 Thread Michael Bach
Dear R Developers, DISCLAIMER: I am new to package development in R and new to this list. I am trying to do something along the lines of: SEXP test_fun (SEXP filename) { const char *inputfile = translateChar(STRING_ELT(filename, 0)); int abc = some_function(inputfile); ... } The code comp

Re: [Rd] .Call interface: Use R SEXP as C mutable *char

2013-03-01 Thread Simon Urbanek
Michael, On Mar 1, 2013, at 4:53 PM, Michael Bach wrote: > Dear R Developers, > > > DISCLAIMER: I am new to package development in R and new to this list. > > I am trying to do something along the lines of: > > SEXP test_fun (SEXP filename) { > > const char *inputfile = translateChar(STRING_