[Rd] Problem using findVar( ) in combination with R's lazy evaluation

2009-08-20 Thread MarcelK
Hi All, I have a few small questions about the usage of the C findVar( ) function when used in C code called with '.Call'. In my case I create an R function with an argument. This function calls some C code in which I use findVar( ) to retrieve the values from the argument. Ofcourse normally I wo

Re: [Rd] Problem using findVar( ) in combination with R's lazy evaluation

2009-08-20 Thread Simon Urbanek
Marcel, On Aug 20, 2009, at 8:41 , MarcelK wrote: I have a few small questions about the usage of the C findVar( ) function when used in C code called with '.Call'. In my case I create an R function with an argument. This function calls some C code in which I use findVar( ) to retrieve the

Re: [Rd] S4: inheritance of validity methods? + Inconsistency in order of validity checks.

2009-08-20 Thread Vitalie S.
With the help of Martin Morgan here is the solution for the above question. First create VIRTUAL class with all the test for children classes: setClass("TESTS", validity=function(object) { cat("Validity here:", class(object), "\n") TRUE }) .simple <- function(object) { cat("No valid

Re: [Rd] Problem using findVar( ) in combination with R's lazy evaluation

2009-08-20 Thread Duncan Murdoch
On 8/20/2009 8:41 AM, MarcelK wrote: Hi All, I have a few small questions about the usage of the C findVar( ) function when used in C code called with '.Call'. In my case I create an R function with an argument. This function calls some C code in which I use findVar( ) to retrieve the values fro

[Rd] Documentation of ties.method argument in `rank`

2009-08-20 Thread Stavros Macrakis
In R 2.9.1/Windows, ? rank says: Usage: rank(x, na.last = TRUE, ties.method = c("average", "first", "random", "max", "min")) Arguments: ... ties.method: a character string specifying how ties are treated, see 'Details'; can be abbreviated. This appears contradictory --

[Rd] header containing (PR#13834)

2009-08-20 Thread mrg
This problem arises on Solaris because apparently Solaris 10 returns the error "ENOSYS" when you try to make a directory on an automount point (translates to "unsupported file system operation"). The R mkdir function invokes do_dircreate in platform.c. The logic in this function, when the rec

[Rd] R installation problem with recommended packages (PR#13899)

2009-08-20 Thread uwe_f_mayer
Full_Name: Uwe F. Mayer Version: 2.9.1 OS: SunOS myhost 5.10 Generic_120012-14 i86pc i386 i86pc Solaris Submission from: (NULL) (216.113.168.130) Standard configuration (that is, not specifying --without-recommended-packages) leads to the following error: gmake[2]: Leaving directory `/usr/local/

[Rd] R compilation problem on 64 bit SunOS (PR#13898)

2009-08-20 Thread uwe_f_mayer
Full_Name: Uwe F. Mayer Version: 2.9.1 OS: SunOS myhost 5.10 Generic_120012-14 i86pc i386 i86pc Solaris Submission from: (NULL) (216.113.168.130) With the change of the NLS handling from 2.9.0 to 2.9.1 the compilation breaks, even as I do specifically not request nls. Specifics: gcc -v Using b

Re: [Rd] R compilation problem on 64 bit SunOS (PR#13898)

2009-08-20 Thread Prof Brian Ripley
You are reporting a Solaris error to R-bugs. If the Solaris libintl.h is broken (and it seems yours is), then you need to try one that works (e.g. OpenCSW) or force the use of the one in the R sources by --with-included-gettext use the GNU gettext library included here or dlsable NLS (see b