> Kirill Müller
> on Wed, 11 May 2016 10:42:56 +0200 writes:
> My ulimit package exposes this API ([1], should finally submit it to
> CRAN); unfortunately this very API seems to be unsupported on OS X
> [2,3]. Last time I looked into it, neither of the documented setting
>
> on Wed, 11 May 2016 23:00:20 -0700 writes:
> Dear R Developers,
> I wrote to this list a week ago with some patches that fix bugs in R's
> GNU Readline interface, but I haven't had a reply. I'm not in a hurry
> but I'd like to make sure that my message is getting
> Richard Cotton
> on Thu, 5 May 2016 09:37:42 +0300 writes:
> If you set the "digits17" control option in deparse, you get a lot of
> unnecessary space in the representation of complex numbers.
> > deparse(0 + 0i)
> [1] "0+0i"
> > deparse(0 + 0i, control = "digits17")
> [1] "0 +
On Thu, May 12, 2016 at 9:51 AM, Martin Maechler
wrote:
> My conclusion was I could not use the RAppArmor package.
>
> (But that's wrong: For the rlimit*() functions below, one do
> *NOT* need an AppArmor-enabled version of Linux !)
Yes, it is a relatively recent (unadvertised) feature that th
On Thu, 12 May 2016 12:07:29 +0200
Jeroen Ooms wrote:
> On Thu, May 12, 2016 at 9:51 AM, Martin Maechler
> wrote:
> > My conclusion was I could not use the RAppArmor package.
> >
> > (But that's wrong: For the rlimit*() functions below, one do
> > *NOT* need an AppArmor-enabled version of Lin
I would like to propose that Rf_mkString(NULL) and Rf_mkChar(NULL)
return NA rather than segfault.
Case: the mkString() and mkChar() functions are convenient to wrap
strings returned by e.g. external C libraries into an R vector.
However sometimes a library returns NULL instead of a string when th
R Developers,
Could someone help explain what it means that R is single threaded? I am
trying to understand what is actually going on inside R when users want to
parallelize code. For example, using mclapply or foreach (with some
backend) somehow allows users to benefit from multiple CPUs.
Simi
On 12/05/2016 8:45 AM, Charles Determan wrote:
R Developers,
Could someone help explain what it means that R is single threaded? I am
trying to understand what is actually going on inside R when users want to
parallelize code. For example, using mclapply or foreach (with some
backend) somehow
Charles,
1. Perhaps this question is better directed at the R-help or
R-pacakge-devel mailinglist.
2. It basically means that R itself can only evaluate one R expression at
the time.
The parallel package circumvents this by starting multiple R-sessions and
dividing workload.
Compiled code calle
Thanks for the replies. Regarding the answer by Dirk, I didn't feel like I
still understood the reasoning why mclapply or foreach cannot handle XPtr
objects. Instead of cluttering the SO question with comments I was getting
the impression that this was a limitation inherited with R objects (which
> On 12 May 2016, at 10:03 , Martin Maechler wrote:
>
>>
>>on Wed, 11 May 2016 23:00:20 -0700 writes:
>
>> Dear R Developers,
>> I wrote to this list a week ago with some patches that fix bugs in R's
>> GNU Readline interface, but I haven't had a reply. I'm not in a hurry
>> but I
As others said XPtr is not something in R so Rcpp mailing list would be the
right place for that aspect.
However, it you forget Rcpp and phrase it as an R question, you also get much
closer to the reason and answer. SEXP type is the internal representation of
all objects in R. I assume your que
The R language itself has features that limit how much
mulitthreading/parallel processing can be done. There are functions with
side effects, such as library(), plot(), runif(), <-, and <<- and there are
no mechanisms to isolate them.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Thu, May 12,
On 12 May 2016 at 13:11, Mark van der Loo wrote:
| Charles,
|
| 1. Perhaps this question is better directed at the R-help or
| R-pacakge-devel mailinglist.
|
| 2. It basically means that R itself can only evaluate one R expression at
| the time.
|
| The parallel package circumvents this by star
Thank you Simon for the detailed reply. That explains much more of what I
was looking for from the R side.
Dirk, I'm sorry if I seem hung up on anything here but I am trying to
understand the details. My reply about XPtr or XPtr on arma/Eigen was to
confirm my understanding was correct, which it
On 12 May 2016 at 09:18, Dirk Eddelbuettel wrote:
|
| On 12 May 2016 at 13:11, Mark van der Loo wrote:
| | Charles,
| |
| | 1. Perhaps this question is better directed at the R-help or
| | R-pacakge-devel mailinglist.
| |
| | 2. It basically means that R itself can only evaluate one R expressio
On 12 May 2016 at 09:25, Charles Determan wrote:
| Thank you Simon for the detailed reply. That explains much more of what I was
| looking for from the R side.
|
| Dirk, I'm sorry if I seem hung up on anything here but I am trying to
| understand the details. My reply about XPtr or XPtr on arma
Hi Peter, Martin, and others,
Thanks for your replies.
- The bugs apply to all systems that use GNU Readline, not just Linux
or Arch Linux.
- Readline version 6.3 changed the signal handling so that SIGWINCH is
no longer handled automatically by the library. This means it's not
currently p
Hello:
Is it widely known that objects not explicitly deleted from one
vignette in a package can be available to a second in "R CMD build" and
"R CMD check" but not when the second vignette is built manually, at
least under RStudio on Mac OS X 10.11.4 using R 3.3.0?
For an exa
19 matches
Mail list logo
