> Or is this a bad idea?
I don't like the proposal. I have seen code like the following (in
fact, I have written such code, where I had forgotten a function was
not vectorized) where the error would have been discovered much later
if outer() didn't catch it.
> outer(1:3, 11:13, sum)
Error in
On Sun, Mar 19, 2017 at 9:09 PM, Martyn Plummer wrote:
> I have just added some code to ensure that the compilation fails with an
> informative error message if a specific C++ standard is requested but the
> corresponding compiler has not been defined. Please test this.
I can confirm that (at l
On Sun, Mar 19, 2017 at 9:09 PM, Martyn Plummer wrote:
> I have just added some code to ensure that the compilation fails with an
> informative error message if a specific C++ standard is requested but the
> corresponding compiler has not been defined. Please test this.
Are you sure we shouldn'
> void dnk_c(double *sortedFsample, unsigned long int n, unsigned
long int k, double *dKol)
All arguments to C functions called by .C() must be pointers. Also, R
integers are C ints, not unsigned long ints.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Mon, Mar 20, 2017 at 5:55 AM, Hristo In
> Gebhardt, Albrecht
> on Sun, 19 Mar 2017 09:14:56 + writes:
> Hi,
> the function outer can not apply a constant function as in the last line
of the following example:
>> xg <- 1:4
>> yg <- 1:4
>> fxyg <- outer(xg, yg, function(x,y) x*y)
>> fconstg <- ou
Hello,
Here a small improvement for R.
When you use the function write.table, if the disk is full for example, the
function doesn't return an error and the file is written but truncated.
It can be a source of mistakes because you can then copy the output file
and think everything is ok.
How to r
Hello,
I'm trying to calculate a certain distance estimator for my thesis. I have a
program in C that works fine when I call it with .C() in R, but since
I'm dealing with big matrices like 3x2 it was getting a stack
overflow. Now I have the same program but more efficeintly coded using
mal
