Thank you, changed in R-patched and R-devel now.
On Sun, 8 Mar 2009, manikandan_naraya...@merck.com wrote:
Full_Name: Manikandan Narayanan
Version: 2.8.1
OS: Linux
Submission from: (NULL) (155.91.45.231)
Here is an excerpt from qpois help page (?qpois):
The quantile is left continuous: '
"JC" == John Chambers
on Fri, 06 Mar 2009 14:12:00 -0800
JC> Some modifications have been committed for the r-devel
JC> version today
JC> that modify (essentially, correct a bug in) the communication
JC> of objects
JC> to an S3 method from an S4 class that extends the S3
I've found the discrepancy, so the patched code from current dloess is
now available in R-patched and R-devel.
On Fri, 6 Mar 2009, Prof Brian Ripley wrote:
On Thu, 5 Mar 2009, Benjamin Tyner wrote:
Hi
Nice to hear from you Ryan. I also do not have the capability to debug on
windows; howeve
Dear Uwe and all,
the build service at http://win-builder.r-project.org/ seems to be
down. Do you have any information on whether and when it will be
functional again?
Best Regards,
Gabor
--
Gabor Csardi UNIL DGM
__
R-devel@r-project.org mailing
Hmm, I see what you mean, and I'd be willing to accept that logic if I
could find a single other instance in the R documentation where that
shorthand was used. But I suppose this might be the only instance
where such a shorthand is necessary.
-roger
On Sun, Mar 8, 2009 at 9:30 PM, Kasper Daniel H
Roger D. Peng wrote:
> Hmm, I see what you mean, and I'd be willing to accept that logic if I
> could find a single other instance in the R documentation where that
> shorthand was used. But I suppose this might be the only instance
> where such a shorthand is necessary.
Could you repeat what the
Gábor Csárdi wrote:
Dear Uwe and all,
the build service at http://win-builder.r-project.org/ seems to be
down. Do you have any information on whether and when it will be
functional again?
No idea what happened. The Webserver process dies. Should be running
again. Thanks for your message!
My patch was not particularly great. I think the Peter's alternative
makes (more) sense.
-roger
On Mon, Mar 9, 2009 at 8:47 AM, Peter Dalgaard wrote:
> Roger D. Peng wrote:
>> Hmm, I see what you mean, and I'd be willing to accept that logic if I
>> could find a single other instance in the R do
Hi,
When I call the *switch* function first time, it works. but when I call it
at the second time, it does nothing. The version I use is R version 2.9.0
Under development (unstable) (2009-02-21 r47969)
here is the output:
> organism="human"
> species <- switch(organism,
human <- "Hs
guangchuang yu wrote:
> Hi,
>
> When I call the *switch* function first time, it works. but when I call it
> at the second time, it does nothing. The version I use is R version 2.9.0
> Under development (unstable) (2009-02-21 r47969)
>
>
> here is the output:
>
>> organism="human"
>> specie
This isn't a bug in R.
You are assigning within the switch statement, and it is returning the
first TRUE value (human).
Use "=" not "<-"
species <- switch(organism, human="HS", fly="DM", yeast="SC")
> species
[1] "SC"
HTH
Jeff
On Mon, Mar 9, 2009 at 8:55 AM, guangchuang yu wrote:
> Hi,
>
> W
But Why ?
Why can not use "<-" ?
On Mon, Mar 9, 2009 at 10:31 PM, Jeff Ryan wrote:
> This isn't a bug in R.
>
> You are assigning within the switch statement, and it is returning the
> first TRUE value (human).
>
> Use "=" not "<-"
>
> species <- switch(organism, human="HS", fly="DM", yeast="SC
Because "<-" assigs a value. It does not name the alternatives.
Again, please read ?switch.
These two examples are the same:
> organism <- 'foo'
> (species <- switch(organism, human <- "HS", fly <- "DM", yeast <- "SC"))
[1] "HS"
> (species <- switch(organism, "HS", "DM", "SC"))
[1] "HS"
Josh
--
> 2. R CMD check gives dozens of warnings ...
Yes, I see a lot of warnings too, but I think that they can and should be
ignored.
1. There is a set where the generic function has "..." and my realization of
the generic has a named argument. But this is exactly what the ... is for in a
generi
Full_Name: Dominique Soudant
Version: 2.4.1
OS: Winbdows
Submission from: (NULL) (134.246.54.61)
R 2.4.1
boot 1.2-27
Let us consider the following example with 8 strata, one observation for each :
> library(boot)
> df <- data.frame(Values=runif(8),month=1:8)
> df
Values month
1 0.0272154
As Yohan points out, and as we found in testing CRAN packages, there are
a number of examples where programmers have written S3 methods for S4
classes, such as print.aTest() below.
This may well have seemed an easy and convenient mechanism, but it is a
design error with potentially disastrous c
On 3/9/2009 11:29 AM, Terry Therneau wrote:
2. R CMD check gives dozens of warnings ...
Yes, I see a lot of warnings too, but I think that they can and should be
ignored.
1. There is a set where the generic function has "..." and my realization of
the generic has a named argument. But thi
Duncan Murdoch wrote:
On 3/9/2009 11:29 AM, Terry Therneau wrote:
2. R CMD check gives dozens of warnings ...
Yes, I see a lot of warnings too, but I think that they can and
should be ignored.
1. There is a set where the generic function has "..." and my
realization of the generic has a
Duncan,
When
The generic solve method has "(a, b, ...)"
I have "solve.gchol(a, b, full=TRUE, ...)"
I was assuming that I would still get an error from CMD check. These are the
ones that I argued as "unavoidable".
But... I just checked, and none of those were the squawkers, only t
Tested in: R version 2.8.1 (2008-12-22) / Windows
Recursive default argument references normally give nice clear errors.
In the first set of examples, you get the error:
Error in ... :
promise already under evaluation: recursive default argument
reference or earlier problems?
(function(a
Now multi-core machines are more widely available, we have gotten to
stress-test the parallel building capabilities of R and of packages.
The current Windows and Mac build machines are both 8-core and I test
on an 8-core machine. These are all fairly recent changes of hardware
and the followin
Stavros Macrakis wrote:
> Tested in: R version 2.8.1 (2008-12-22) / Windows
>
> Recursive default argument references normally give nice clear errors.
> In the first set of examples, you get the error:
>
> Error in ... :
> promise already under evaluation: recursive default argument
> referenc
On Mon, Mar 9, 2009 at 5:40 PM, Wacek Kusnierczyk
wrote:
> Stavros Macrakis wrote:
>> Tested in: R version 2.8.1 (2008-12-22) / Windows
> when i run these examples, the execution seems to get into an endless
> loop with no error messages whatsoever. how much time does it take
> before you get th
Stavros Macrakis wrote:
> On Mon, Mar 9, 2009 at 5:40 PM, Wacek Kusnierczyk
> wrote:
>
>> Stavros Macrakis wrote:
>>
>>> Tested in: R version 2.8.1 (2008-12-22) / Windows
>>>
>
>
>> when i run these examples, the execution seems to get into an endless
>> loop with no error messag
Stavros Macrakis wrote:
Tested in: R version 2.8.1 (2008-12-22) / Windows
Recursive default argument references normally give nice clear errors.
In the first set of examples, you get the error:
Error in ... :
promise already under evaluation: recursive default argument
reference or earlier
On Mon, Mar 9, 2009 at 8:55 AM, guangchuang yu
asked why switch(..., a <- 3, ...) doesn't
have the same effect as switch(..., a=3, ...).
In most contexts, `<-` and `=` are synonymous in R, and mean
assignment. In function-argument position, however, an infix `=` names
the argument. Switch depend
Greetings -
Thanks for the response and apologies for the delay.
I was actually unable to get even the example script for Rd2HTML to work in
2.9.0dev, which may be due to my lack of general programming savvy, or
possibly my working on a windows machine? In the meantime I found a
workaround to ad
27 matches
Mail list logo
