Dear list members (esp. Duncan),
I've run into the following curious problem with Version 2.2.0 alpha for
Windows: Options in the Profile file in R's etc directory don't appear to be
set. (I habitually uncomment options(chmhelp=TRUE), to no effect in this
case.) As far as I can see, the only thin
First of all, thanks to those who've set up R to work so smoothly with
Miktex-- even a total Latex bunny like me got it to work instantly, so
that for the first time I'm able to run my Rd files through the Latex
side of RCMD CHECK.
Now the question/buglet. One of my Rd files contains the following
This problem was brought up by Xu Neng <[EMAIL PROTECTED]> in the rpy-list.
Remember the old times when computer guys thought the year 2000 was
too far away to be worried? In my case, the dates like "-06-6" and
"-09-09" are used as special missing codings for dates.
If R cannot handle d
I agree: no function should per default touch the random number
stream. Otherwise this will undoubtedly lead to misuse. And while one
may want to include a seed argument in case a user wants to set it
explicitly, I would argue that the preferred usage is to do
set.seed(SOMETHING)
someFu
Could acf() in R-2.2.0 please be made generic?
Thanks,
Paul Gilbert
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Could loadings() in R-2.2.0 please be made generic?
Thanks,
Paul Gilbert
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Prof Brian Ripley wrote:
>
> What does anyone want such dates for? I hope there was an extremely good
> reason to spend other people's time on this, and look forward to an
> extremely convincing explanation.
>
I can think of one case where I've seen exact dates that far in the
future used: as
On Wed, 14 Sep 2005, Uwe Ligges wrote:
> Bo Peng wrote:
>
>>> Well, bug, if you really want to call it a bug that you cannot represent
>>> the year . ;-)
>>
>>
>> So I guess we need a warning message and a line in help(as.Date)?
>
> Even better a fix (than an *error* message), since the POSIX
BTW, I think there is a problem with the way the argument "seed" is used
in the new simulate in stats. The problem is that repeated calls to
simulate using the default argument will introduce a new pattern into
the RNG:
> stats:::simulate
function (object, nsim = 1, seed = as.integer(runif(1,