Re: [Rd] When collected warnings exceeds 50

2011-11-16 Thread Prof Brian Ripley
Fixed (in a different way) in R-devel/R-patched. On Thu, 10 Nov 2011, Jeffrey Horner wrote: On Thu, Nov 10, 2011 at 10:54 PM, Jeffrey Horner wrote: Hi, I've been tracking down a memory leak in an rApache application, http://data.vanderbilt.edu/rapache/bbplot. The code was deployed in 2007 an

Re: [Rd] cygwin R-2.14.0 build fail

2011-11-16 Thread marco atzeri
On 11/12/2011 3:25 PM, Mark Carter wrote: I tried to build R-2.14.0 on cygwin using the commands: ./configure --with-x=no make I started to get a whole lot of errors starting with: /cygdrive/c/Users/mcarter/src/R-2.14.0/src/modules/internet/Rhttpd.c:275: undefined reference to `_R_InputHandlers

[Rd] Injecting source reference from external editors (emacs).

2011-11-16 Thread Vitalie Spinu
Hi everyone, I would like to inject source reference into R objects from external editor. In my case it's emacs with ESS and ess-tracebug (http://code.google.com/p/ess-tracebug/). Currently the user has to source the file before the src references become available. I would like to spare her, a

Re: [Rd] Question on parsing R code from C

2011-11-16 Thread KR
Simon Urbanek r-project.org> writes: > Not without seeing the actual code. (And details such as which platform > you're on). > Note that setup_Rmainloop() is the last to set the SETJMP context target so you should make sure the stack is > still present after it finished (i.e. you can't call it

Re: [Rd] Question on parsing R code from C

2011-11-16 Thread Simon Urbanek
On Nov 16, 2011, at 2:48 PM, KR wrote: > Simon Urbanek r-project.org> writes: >> Not without seeing the actual code. (And details such as which platform >> you're > on). >> Note that setup_Rmainloop() is the last to set the SETJMP context target so > you should make sure the stack is >> still

Re: [Rd] cygwin R-2.14.0 build fail

2011-11-16 Thread Prof Brian Ripley
The failures are *not* minor. Please don't distribute an R linked to a broken BLAS library. Those tests are not for fun: they came from real errors on real problems. On Wed, 16 Nov 2011, marco atzeri wrote: On 11/12/2011 3:25 PM, Mark Carter wrote: I tried to build R-2.14.0 on cygwin using

Re: [Rd] cygwin R-2.14.0 build fail

2011-11-16 Thread marco atzeri
On 11/16/2011 9:32 PM, Prof Brian Ripley wrote: The failures are *not* minor. Please don't distribute an R linked to a broken BLAS library. Those tests are not for fun: they came from real errors on real problems. Dear Brian, I am reasonable sure that the cygwin blas library are fine, have you

[Rd] strange behavior from cex="*"

2011-11-16 Thread Ben Bolker
Someone inquired on StackOverflow about apparently non-deterministic graphics behaviour in R. I noticed that they were using cex="*" and discovered some potentially weird behavior. On repeated runs of the same code I can get different PNGs. If I set the number of runs high enough, I seem to

Re: [Rd] cygwin R-2.14.0 build fail

2011-11-16 Thread peter dalgaard
On Nov 16, 2011, at 22:08 , marco atzeri wrote: > On 11/16/2011 9:32 PM, Prof Brian Ripley wrote: >> The failures are *not* minor. Please don't distribute an R linked to a >> broken BLAS library. Those tests are not for fun: they came from real >> errors on real problems. >> > > Dear Brian, > I

Re: [Rd] strange behavior from cex="*"

2011-11-16 Thread Kevin R. Coombes
Hi Ben, Just a few things to add. First, the same phenomenon occurs when you use any character string as the value of cex; there is nothing special about "*". Second, you cannot get this phenomenon by trying to do something like par(cex="*") because the par function actually checks if the

Re: [Rd] strange behavior from cex="*"

2011-11-16 Thread peter dalgaard
On Nov 16, 2011, at 22:38 , Ben Bolker wrote: > Someone inquired on StackOverflow about apparently non-deterministic > graphics behaviour in R. I noticed that they were using cex="*" and > discovered some potentially weird behavior. It can be reproduced much more simply (well, not the hang, bu

Re: [Rd] strange behavior from cex="*"

2011-11-16 Thread Ben Bolker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11-11-16 05:18 PM, peter dalgaard wrote: > > On Nov 16, 2011, at 22:38 , Ben Bolker wrote: > >> Someone inquired on StackOverflow about apparently non-deterministic >> graphics behaviour in R. I noticed that they were using cex="*" and >> discov

Re: [Rd] strange behavior from cex="*"

2011-11-16 Thread Joris Meys
On Wed, Nov 16, 2011 at 11:26 PM, Ben Bolker wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 >  It's mildly surprising to me that people can continue to find odd > cases like this after more than 10 years (and imagine how many > cumulative hours of R use ...) Mildly surprising? It's asto

Re: [Rd] cygwin R-2.14.0 build fail

2011-11-16 Thread marco atzeri
On 11/16/2011 11:04 PM, peter dalgaard wrote: On Nov 16, 2011, at 22:08 , marco atzeri wrote: On 11/16/2011 9:32 PM, Prof Brian Ripley wrote: The failures are *not* minor. Please don't distribute an R linked to a broken BLAS library. Those tests are not for fun: they came from real errors on

Re: [Rd] strange behavior from cex="*"

2011-11-16 Thread Duncan Murdoch
On 11-11-16 5:26 PM, Ben Bolker wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11-11-16 05:18 PM, peter dalgaard wrote: On Nov 16, 2011, at 22:38 , Ben Bolker wrote: Someone inquired on StackOverflow about apparently non-deterministic graphics behaviour in R. I noticed that they

[Rd] inaccuracy in man page for duplicated() + anyDuplicated() not working with MARGIN=0

2011-11-16 Thread Hervé Pagès
Hi, In man page for duplicated: Value: ‘duplicated()’: For a vector input, a logical vector of the same length as ‘x’. For a data frame, a logical vector with one element for each row. For a matrix or array, a logical array with the same dimensions and dimnames. When 'x