> On Fri, Aug 21, 2015 at 8:38 PM, Radford Neal wrote:
>
> > The reason for this appears to be that the omp.h file included is
> > appropriate only for the 32-bit version of the openMP library. As
> > far as I can see, there is no 64-bit version of this include file
> > in the stuff installed wi
Hi Radford
On Fri, Aug 21, 2015 at 8:38 PM, Radford Neal wrote:
>
> I've been getting pqR to work on windows systems, and in the process
> have discovered various problems with R core versions of R and with
> Rtools.
We happen to be working on a new version of the windows tool chain,
perhaps yo
Dear R community,
I have been working on speeding up a few parts of the methods package and
related environment/namespace functionality. I would like to get some
community input on a few proposed changes that are rather small, but do
involve deprecations. These changes would simplify and speed-up
> Does R have a function like the S/S++ unset() function?
That should be 'S+' or 'S-Plus', not the typo 'S++'.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Fri, Aug 21, 2015 at 1:43 PM, William Dunlap wrote:
> Does R have a function like the S/S++ unset() function?
> unset(name) would remov
Does R have a function like the S/S++ unset() function?
unset(name) would remove 'name' from the current evaluation
frame and return its value. It allowed you to safely avoid
some memory copying when calling .C or .Call.
E.g., suppose you had C code like
#include
#include
SEXP add1(SEXP p
Along with getting pqR to work on Windows, I've also been testing it
in the context of embedded R, and in the process have found some
problems with the examples given of embedded R use.
One problem can be seen in R_ReplDLLinit, in src/main/main.c:
void R_ReplDLLinit(void)
{
SETJMP(R_Toplevel
When getting pqR to work on Windows, I've wanted for it to be able to
use SSE2 instructions with 32-bit builds, for those 32-bit processors
that have SS2 instructions (all of them from the Pentium 4 onwards).
It seems that R Core 32-bit versions do not attempt this, instead
using the 387 FPU for a
Continuing with problems that I've uncovered while getting pqR to work
on Windows...
The file src/ghuwin32/psignal.c (used only in Windows builds) fails to
use the sigset_t type in all places where it should, using "int" some
places instead.
Here is a diff of the needed corrections:
@@ -253,7 +
I've been getting pqR to work on windows systems, and in the process
have discovered various problems with R core versions of R and with
Rtools.
One is with the implementation of OpenMP in 64-bit Rtools. This
problem is in Rtools215 and Rtools33, and presumably all the ones in
between. You can s
Dear both,
I have just found that names are treated in the same way in optim() depending
on the optimization method. The example below shows the difference between the
Brent method and the L-BFGS-B method.
f <- function(x){ y <- x^2;names(y) <-"f(x)";y}
optim(10, f, method="Brent", lower=-1, up
10 matches
Mail list logo
