[Rd] Sharing variables in seperate workspace

2009-04-20 Thread Philip
Hi all. I'm for the first time trying to make a library in R 2.8.1 on Ubuntu Linux. The library is very simple, R functions just need to share a variable (that is defined in the R code) and maybe functions and export functions for the user to .GlobalEnv. This variable should only be directly acce

Re: [Rd] print.closure at the R level

2009-04-20 Thread Martin Maechler
> "RF" == Romain Francois > on Mon, 20 Apr 2009 22:42:22 +0200 writes: RF> Hello, RF> Sorry if I have waisted any time of people truing this RF> patch. yes, you did waste (sic) but thank you for the code suggestions anyway. RF> There was an issue with debuggin

Re: [Rd] bug in classesToAM()

2009-04-20 Thread Hervé Pagès
Thanks! H. John Chambers wrote: Yes, thanks. Should be fixed now in r-devel and 2.9.0 patched. John hpa...@fhcrc.org wrote: Hi, I can't get the non-abbreviated class names of the rows and the cols of the Adjacency Matrix: setClass("ClassWithALongName") setClass("SubclassOfClassWithALongN

Re: [Rd] print.closure at the R level

2009-04-20 Thread Romain Francois
Hello, Sorry if I have waisted any time of people truing this patch. There was an issue with debugging (use of debug and browser that caused an infinite recursion). I think this is now fixed. At the R level, I have now this : > print.function function (x, useSource = TRUE, ...) { invisib

Re: [Rd] suggestion for R >= 3.0: computer-readable CHANGELOG

2009-04-20 Thread Max Kuhn
On Fri, Apr 17, 2009 at 2:09 PM, Philippe Grosjean wrote: > OK, then, I catch the practical point of view that is: nobody will use it > and we cannot force people to use it. So, it means that we should think > about tools to *automatically* generate a limited set of entries in the > CHANGELOG. Of

[Rd] Problems building R 2.9.0... on SGI and Sun once again

2009-04-20 Thread Atro Tossavainen
I've successfully built R 2.9.0 on Linux (amd64, i386 and ppc), but am having a bit of trouble with legacy boxen. What should have gone into the variable that is empty at the time it is used in "for f in $SOMETHING" and why does it end up being empty? Solaris 8 with Sun Studio 11 compilers: buil

Re: [Rd] R build fails during make when configured with "--with-x=no" (PR#13666)

2009-04-20 Thread P . Dalgaard
j...@ku.edu wrote: >=20 > If R is configured using the "--with=3Dx=3Dno" option, then the make fa= ils with the > following error: > make[1]: *** [R] Error 1 > make[1]: Leaving directory `/home/jeet/Scratch/r-build/on-frontend/R-2.= 9.0/src' > make: *** [R] Error 1 >=20 > The problem appears

Re: [Rd] R build fails during make when configured with "--with-x=no" (PR#13665)

2009-04-20 Thread Peter Dalgaard
j...@ku.edu wrote: > > If R is configured using the "--with=x=no" option, then the make fails with > the > following error: > make[1]: *** [R] Error 1 > make[1]: Leaving directory > `/home/jeet/Scratch/r-build/on-frontend/R-2.9.0/src' > make: *** [R] Error 1 > > The problem appears to be

Re: [Rd] ave returns wrong data type (PR#13664)

2009-04-20 Thread Dimitris Rizopoulos
Note that according to ?ave, the first argument of ave(), 'x' should be a *numeric* vector. In your case 'x' is not numeric, it is a character vector. So I think that ave() works as documented, i.e., if you supply as first argument a numeric vector, then you do get as an output a numeric vector

[Rd] R build fails during make when configured with "--with-x=no" (PR#13665)

2009-04-20 Thread jeet
Full_Name: Jeet Sukumaran Version: 2.9.0 OS: OS X / Rocks 5.1 Submission from: (NULL) (66.45.136.241) If R is configured using the "--with=x=no" option, then the make fails with the following error: make[4]: Entering directory `/home/jeet/Scratch/r-build/on-frontend/R-2.9.0/src/modules/vfonts'

[Rd] ave returns wrong data type (PR#13664)

2009-04-20 Thread brenbarn
Full_Name: Brendan Barnwell Version: 2.9.0 OS: Windows XP Pro Submission from: (NULL) (71.102.131.29) The ave() function returns an incorrect datatype. Specifically, ave(x, g, f) always returns a vector with the same mode as x, rather than using the mode of the vector returned by f. Observe: