Re: [Rd] R-beta on AIX5.2

2005-12-13 Thread Prof Brian Ripley
Thank you. To avoid error messages on other platforms, we will use #ifdef calloc # undef calloc #endif (and similarly for free for completeness). On Wed, 14 Dec 2005, Ei-ji Nakama wrote: > I build R-beta on AIX5.2 is failed. > > make[3]: Entering directory > `/home/nakama/Rbeta/R-beta/src/nmat

[Rd] R-beta on AIX5.2

2005-12-13 Thread Ei-ji Nakama
I build R-beta on AIX5.2 is failed. make[3]: Entering directory `/home/nakama/Rbeta/R-beta/src/nmath' xlc_r -I. -I../../src/include -I../../src/include -I/usr/local/include -I/opt/freeware/include -DHAVE_CONFIG_H -q64 -I/usr/local/include -I/opt/freeware/include -O2 -D_ALL_SOURCE -D_LINUX_SOURCE

Re: [Rd] Building R with f2c - still needed?

2005-12-13 Thread Dirk Eddelbuettel
On Tue, Dec 13, 2005 at 09:48:56PM +, Prof Brian Ripley wrote: > Does anyone have a need to use f2c rather than a Fortran compiler to build > R? We used f2c up until a few months ago as a last line of defence against crappy Fg77 code on m68k/arm (one or both, it changed at times). I'd be hes

Re: [Rd] Building R with f2c - still needed?

2005-12-13 Thread Peter Dalgaard
Prof Brian Ripley <[EMAIL PROTECTED]> writes: > Does anyone have a need to use f2c rather than a Fortran compiler to build > R? > > It is yet one more thing to test, and as it only works on 32-bit platforms > it is something that I will shortly no longer be able to test. The only candidate th

[Rd] Building R with f2c - still needed?

2005-12-13 Thread Prof Brian Ripley
Does anyone have a need to use f2c rather than a Fortran compiler to build R? It is yet one more thing to test, and as it only works on 32-bit platforms it is something that I will shortly no longer be able to test. -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied St

Re: [Rd] R_PROFILE on Windows

2005-12-13 Thread Prof Brian Ripley
On Tue, 13 Dec 2005, Fernando Henrique Ferraz P. da Rosa wrote: >There seems to be a bug in the Startup section, regarding the > R_PROFILE environment variable in Windows. If not a bug in the Startup > itself, perhaps a bug in the documentation. Nope, it works as documented, using exactly

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)

2005-12-13 Thread Prof Brian Ripley
?"[" says See Also: 'list', 'array', 'matrix'. '[.data.frame' and '[.factor' for the behaviour when applied to data.frame and factors. 'Syntax' for operator precedence, and the _R Language_ reference manual about indexing details. and the `indexing details' are in

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)

2005-12-13 Thread ggrothendieck
The other place its discussed is in 3.4.1 of the R Language Definition: http://finzi.psych.upenn.edu/R/doc/manual/R-lang.html#Indexing-by-vectors On 12/13/05, Tony Plate <[EMAIL PROTECTED]> wrote: > Yes, 0/1 (numeric) are intended to be used as index vectors -- and they > have the semantics of nu

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)

2005-12-13 Thread Gabor Grothendieck
The other place its discussed is in 3.4.1 of the R Language Definition: http://finzi.psych.upenn.edu/R/doc/manual/R-lang.html#Indexing-by-vectors On 12/13/05, Tony Plate <[EMAIL PROTECTED]> wrote: > Yes, 0/1 (numeric) are intended to be used as index vectors -- and they > have the semantics of nu

[Rd] R_PROFILE on Windows

2005-12-13 Thread Fernando Henrique Ferraz P. da Rosa
Dear R-devel, There seems to be a bug in the Startup section, regarding the R_PROFILE environment variable in Windows. If not a bug in the Startup itself, perhaps a bug in the documentation. According to ?Startup: Then R searches for the site-wide startup profile unless

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389)

2005-12-13 Thread ripley
It is peculiar behaviour on your part, but the developers do not find it at all `funny'. On Tue, 13 Dec 2005 [EMAIL PROTECTED] wrote: > Full_Name: Axel Rasche > Version: 2.2.0 > OS: Linux > Submission from: (NULL) (141.14.21.81) > > > Dear Debuggers, > > This is not a serious problem. Are 0/1 ve

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389)

2005-12-13 Thread rasche
Hi, OK, no bug. I got stuck into to much indexing. Now I understand this point definitely better. Sorry for disturbing you, Axel Tony Plate wrote: > Yes, 0/1 (numeric) are intended to be used as index vectors -- and they > have the semantics of numeric indices, which is that 0 elements in the

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)

2005-12-13 Thread Tony Plate
Yes, 0/1 (numeric) are intended to be used as index vectors -- and they have the semantics of numeric indices, which is that 0 elements in the index are omitted from the result. This can be a very useful mode of operation in many situations. I was going to write "This is described in both the

Re: [Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389)

2005-12-13 Thread Peter Dalgaard
[EMAIL PROTECTED] writes: > Full_Name: Axel Rasche > Version: 2.2.0 > OS: Linux > Submission from: (NULL) (141.14.21.81) > > > Dear Debuggers, > > This is not a serious problem. Are 0/1 vectors intended to be used as index > vectors? If yes, there is a bug. If not, it leads just to some funny b

[Rd] 0/1 vector for indexing leads to funny behaviour (PR#8389)

2005-12-13 Thread rasche
Full_Name: Axel Rasche Version: 2.2.0 OS: Linux Submission from: (NULL) (141.14.21.81) Dear Debuggers, This is not a serious problem. Are 0/1 vectors intended to be used as index vectors? If yes, there is a bug. If not, it leads just to some funny behaviour rather than an error message. In the

[Rd] correct address for R-bugs ..

2005-12-13 Thread Martin Maechler
> "Greg" == Gregory Warnes <[EMAIL PROTECTED]> > on Mon, 12 Dec 2005 14:03:00 -0500 writes: Greg> I got an email error message when I attempted to Greg> send this from my work account. I have manually Greg> added it to the bug tracker, and am resending from Greg> my pe