On 13 Mar 2014, at 21:08 , Steven McKinney wrote:
> Checking CRAN today, I see that on the Sources page
>
> http://cran.r-project.org/sources.html
>
> that R-3.0.2.tar.gz is still there. R-3.0.3.tar.gz is available from the
> Older releases are available >>here<<. hyperlink to
>
> http:/
Hi
Is there a way to detect that the process that corresponds to a pipe has
ended? On my system (Ubuntu 13.04), I see
> p <- pipe("true", "w"); Sys.sleep(1); system("ps -elf | grep true |
grep -v grep"); isOpen(p)
[1] TRUE
The "true" process has long ended (as the filtered ps system call em
On Mar 14, 2014, at 8:09 AM, Kirill Müller
wrote:
> Hi
>
> Is there a way to detect that the process that corresponds to a pipe has
> ended? On my system (Ubuntu 13.04), I see
>
> > p <- pipe("true", "w"); Sys.sleep(1); system("ps -elf | grep true | grep -v
> > grep"); isOpen(p)
> [1] TRUE
>
On 03/14/2014 03:54 PM, Simon Urbanek wrote:
As far as R is concerned, the connection is open. In addition, pipes exist even
without the process - you can close one end of a pipe and it will still exist
(that’s what makes pipes useful, actually, because you can choose to close
arbitrary combin
On Mar 14, 2014, at 11:03 AM, Kirill Müller
wrote:
> On 03/14/2014 03:54 PM, Simon Urbanek wrote:
>> As far as R is concerned, the connection is open. In addition, pipes exist
>> even without the process - you can close one end of a pipe and it will still
>> exist (that’s what makes pipes usef
Dear R-devel,
Question:
How can I get Sweave to recognize that the \thebibliography section
is already created and generate the vignette pdf with a single pass? Or
is there a way to let R CMD build know that Sweave needs to be run twice?
If (1) is not possible, any suggestions how t
On 14/03/2014 12:28 PM, Skye Bender-deMoll wrote:
Dear R-devel,
Question:
How can I get Sweave to recognize that the \thebibliography section
is already created and generate the vignette pdf with a single pass? Or
is there a way to let R CMD build know that Sweave needs to be run twice?
Hi,
I'm using valgrind to check over some C/C++ code for an R library. I'm
getting the report (see below), but can't track down the uninitialised
value(s). I tried using --track-origins=yes in valgrind which gives:
==28258== Uninitialised value was created by a stack allocation
==28258==
On 14/03/2014 17:56, Jarrod Hadfield wrote:
Hi,
I'm using valgrind to check over some C/C++ code for an R library. I'm
R package?
getting the report (see below), but can't track down the uninitialised
value(s). I tried using --track-origins=yes in valgrind which gives:
==28258== Uninitial
