On Sun, 25 Jun 2006, Jeff Barrett wrote:
> Hello,
> I am a biostats student and a newbie to R. I have a question about
> 32-bit vs. 64-bit.
> I am running FC5 on a AMD 3800+ with 2GB Ram. With 64-bit, I am
> running into some issues the stability of FC5. A friend suggested I
> ditch the 64-bit
Hello,
I am a biostats student and a newbie to R. I have a question about
32-bit vs. 64-bit.
I am running FC5 on a AMD 3800+ with 2GB Ram. With 64-bit, I am
running into some issues the stability of FC5. A friend suggested I
ditch the 64-bit version of FC5 for the 32-bit. I do not current
Believe it or not, it works either way: I haven't fully
figured out the logic yet (except to note that I had the
logic reversed below):
Ops.Date <- function (e1, e2)
{
if (nargs() == 1)
stop("unary ", .Generic, " not defined for Date objects")
boolean <- switch(.Generic,
Hello,
I want to use withCallingHandlers(expr, warning = function(w) { }),
that is, to use a custom warning handler. I want this handler to
replicate the behavior of the usual handler. I have problems with the
mode 'options(warn = 0)' where the warnings are delayed, except if
calling 'war
Wolfram,
SuSE 8.2 is _very_ old. Why not just upgrade to SuSE 10.1, where
R-2.3.1 compiles with no problems?
Ted Catchpole
[EMAIL PROTECTED] wrote:
> --gKMricLos+KVdGMg
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> I compiled R 2.3.1 on two SuSE systems.
> With
