[Rd] R Startup configuration file

2010-02-10 Thread Barry Rowlingson
Currently when R starts up it can be configured by a file of environment variable specifications and a file of R code. This makes programmatic modification of startup configuration tricky. Case in point: I start R, do install.packages("foo"), and up pops the 'choose a CRAN mirror' dialog. I'd like

Re: [Rd] R Startup configuration file

2010-02-10 Thread Duncan Murdoch
Barry Rowlingson wrote: Currently when R starts up it can be configured by a file of environment variable specifications and a file of R code. This makes programmatic modification of startup configuration tricky. Case in point: I start R, do install.packages("foo"), and up pops the 'choose a CRA

[Rd] system.time provides inaccurate sys.child (PR#14210)

2010-02-10 Thread manuel . lopez-ibanez
Full_Name: Manuel López-Ibáñez Version: R version 2.6.2 (2008-02-08) OS: linux-gnu Submission from: (NULL) (164.15.10.156) This is only relevant for CPU intensive child processes. Otherwise, the problem is not obvious. Therefore, we need a CPU intensive program like this one: /

[Rd] incoming/14210 system.time provides inaccurate sys.child

2010-02-10 Thread Manuel López-Ibáñez
Patch against current trunk attached. It is a one-liner, so I do not believe anyone can claim copyright over it. Cheers, Manuel. BTW, bugs.r-project.org is painfully slow. I cannot login, I cannot post messages, I cannot attach files. And it doesn't handle accents in my name. --- sys-u

Re: [Rd] R Startup configuration file

2010-02-10 Thread Barry Rowlingson
On Wed, Feb 10, 2010 at 11:44 AM, Duncan Murdoch wrote: > When I read the ?Startup man page, I find it is too complicated already; I > don't want to add another kind of file to read.  (Would we have  separate > user and site versions of this new file?  When would it be handled?) > > However, we c

Re: [Rd] (PR#14210) incoming/14210 system.time provides inaccurate

2010-02-10 Thread P . Dalgaard
Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez wrote: > Patch against current trunk attached. It is a one-liner, so I do not > believe anyone can claim copyright over it. Fixed for r-devel (r51115). > Cheers, >=20 > Manuel. >=20 > BTW, bugs.r-project.org is painfully slow. I cannot login, I cannot pos=

[Rd] R crashes when setWinProgressBar is give a numeric value for label argument

2010-02-10 Thread Greg Snow
This problem can be seen by the following commands: > pb <- winProgressBar(max=1000, label='0') > b <- 1 > setWinProgressBar(pb, b, label=b) This set of commands (on windows of course, XP in this case) causes R to crash. This is not strictly a bug since the documentation states that the label a

[Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread cstrato
Dear Debian/Ubuntu experts, For the second time users of my BioC package reported problems when trying to compile it on Debian/Ubuntu. The error is always the same: "'wcstombs' was not declared in this scope", see: https://www.stat.math.ethz.ch/pipermail/bioconductor/2010-February/031739.htm

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread Dirk Eddelbuettel
Christian, On 10 February 2010 at 22:02, cstrato wrote: | Dear Debian/Ubuntu experts, | | For the second time users of my BioC package reported problems when | trying to compile it on Debian/Ubuntu. | | The error is always the same: "'wcstombs' was not declared in this | scope", see: | https:

[Rd] Wrong documentation of 'isTRUE' (PR#14212)

2010-02-10 Thread gb
Full_Name: Göran Broström Version: 2.10.1 OS: Ubuntu 9.10 Submission from: (NULL) (85.11.40.53) The documentation for 'isTRUE' states that 'isTRUE(x)' is an abbreviation of 'identical(TRUE, x)', and so is true if and only if 'x' is a length-one logical vector with no attributes (not even n

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread cstrato
Dear Dirk, Thank you for your fast reply. I am afraid that a small self-contained example will not solve the problem, since in this example I would need to add "#include ", and as you can see from: https://stat.ethz.ch/pipermail/bioconductor/2009-August/029192.html adding "#include " to some

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread Prof Brian Ripley
Such errors are common when people use older versions of g++ to write their C++ code. Later versions of g++ have somewhat stricter conformance to the C++ standards and catch some lax usage: we've seen it quite a lot for g++ 4.4.x and even more for pre-4.5.0. In all the cases I have seen this

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread Dirk Eddelbuettel
Christian, On 10 February 2010 at 22:40, cstrato wrote: | Dear Dirk, | | Thank you for your fast reply. | | I am afraid that a small self-contained example will not solve the | problem, since in this example I would need to add "#include | ", and as you can see from: | https://stat.ethz.ch/pi

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread cstrato
Dear Prof. Ripley, Thank you for this extensive explanation. The compiler version of OpenSUSE11.1 is "gcc version 4.3.2" whereas Ubuntu uses "gcc 4.4.1". Interestingly, the first complaint was a Debian testing (squeeze) user with "gcc-4.3". Since my package depends on ROOT I have assumed tha

Re: [Rd] wcstombs error when compiling package with Debian/Ubuntu

2010-02-10 Thread cstrato
Dear Dirk, The compiler version of OpenSUSE11.1 is "gcc version 4.3.2" whereas Ubuntu uses "gcc 4.4.1". Interestingly, the first complaint was a Debian testing (squeeze) user with "gcc-4.3". Since it seems to be a problem of "recent-vs-older g++ versions" I will include the header file. I