Re: [Rd] Why not pthreads on Windows in 'parallel' package?

2015-08-14 Thread Dan Tenenbaum
I'm confused; mclapply does not work on windows (at least with mc.cores > 1) because fork() is not available on windows. So the original question still seems relevant to me. Dan - Original Message - > From: "Henrik Bengtsson" > To: "Kasper Daniel Hansen" > Cc: "R-devel" > Sent: Frida

Re: [Rd] Why not pthreads on Windows in 'parallel' package?

2015-08-14 Thread Henrik Bengtsson
Aaaah ... and argh - I should have better not to post R question at midnight, especially when I know it forks the process and it's not using threads. Brain meltdown. (So, we'll proceed trying to use pthreads in matrixStats also for Windows). Sorry for the noise and thanks Kasper. Henrik On Aug 15

Re: [Rd] Why not pthreads on Windows in 'parallel' package?

2015-08-14 Thread Kasper Daniel Hansen
mclapply uses fork which is different from pthreads. As I understand it, pthreads requires you to rewrite code, fork is a system call which takes care of completely replicating the current state of the process. Kasper On Fri, Aug 14, 2015 at 5:00 PM, Henrik Bengtsson wrote: > On Windows there

[Rd] Why not pthreads on Windows in 'parallel' package?

2015-08-14 Thread Henrik Bengtsson
On Windows there are a few 'pthreads' implementation, e.g. pthreads-w32 and winpthreads [https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-pthreads]. We're thinking of giving them a try for the matrixStats package, and basic tests indicates it works, but since Windows pthreads are no

[Rd] Build R on Haiku

2015-08-14 Thread Joe S
Hi R-devel, I'm trying to get R 3.2.1 working on Haiku (an open source OS inspired by BeOS, not Linux based) on i586. With a few small changes to library paths and ifdefs I am able to get a seemingly working R binary. The build process stops with the 'tools' package. The last lines from make are be

Re: [Rd] capture.output() duplicates last line unless newline (R-devel bug)

2015-08-14 Thread Henrik Bengtsson
Thanks for the updates. I'm glad it was taken care of. I would normally have waited, but I wanted to bring this up asap in case there was a risk for it to enter R 3.2.2. /Henrik On Fri, Aug 14, 2015 at 11:30 AM, peter dalgaard wrote: > The fix for PR#16481 had a side effect involving capture.o

Re: [Rd] capture.output() duplicates last line unless newline (R-devel bug)

2015-08-14 Thread peter dalgaard
The fix for PR#16481 had a side effect involving capture.output(), so this may be transient, please recheck whether the issue has disappeared in the meantime. -pd On 14 Aug 2015, at 11:09 , Henrik Bengtsson wrote: > In R-devel (2015-08-12 r69024), capture.output() incorrectly > duplicates the

Re: [Rd] capture.output() duplicates last line unless newline (R-devel bug)

2015-08-14 Thread Prof Brian Ripley
But it was changed over 24h ago in R-devel, 2 commits later See e.g. https://cran.r-project.org/bin/windows/base/rdevel.html for when not to report on 'R (Under Development)' (and you really should have known that, as a Windows user). On 14/08/2015 10:09, Henrik Bengtsson wrote: In R-de

[Rd] capture.output() duplicates last line unless newline (R-devel bug)

2015-08-14 Thread Henrik Bengtsson
In R-devel (2015-08-12 r69024), capture.output() incorrectly duplicates the last line unless it ends with a newline. I don't see this in R 3.2.2 RC (2015-08-13 r69049). It seems to have started fairily recently; I spotted this yesterday after starting to get errors in my R.utils check that use ca

Re: [Rd] Bug in rank with utf8?

2015-08-14 Thread peter dalgaard
> On 14 Aug 2015, at 08:10 , Prof Brian Ripley wrote: > > E.g. on my Yosemite system in en_US.UTF-8 > >> rank(c(x, y)) > [1] 1.5 1.5 > ..which differs from my Mavericks system but not my Yosemite system, both in en_US.UTF-8, both with icuGetCollate returning "root"... Oh, well. -pd -- Pet