similar to: scan() + error interferes with count.fields() in some cases (PR#248)

Does anybody understand what's going on here: I have the following ascii file called "y.txt" "USD-DEM" "USD-JPY" "DEM-JPY" 0.344901 4.78712 4.442 0.345715 4.7882 4.44189 0.350657 4.79065 4.44177 0.35347 4.79065 4.43616 0.35368 4.78957 4.43622 0.35361 4.78982 4.43669 0.353821 4.79036 4.43622 0.352767 4.78899 4.43634 0.353119 4.78916 4.43545

Our main server [www/ftp/mail] "stat.ethz.ch" (if you want to ping) will be getting more RAM, new disks with new filesystems, etc. This will start on Saturday July 24, 10:30 GMT+2 (=MEST) and last several hours. In case it would take more than 4 hours or so, you might get messages back that you sent to the mailing lists R-help, R-devel, R-announce or R-core. DO NOT REPOST THEM, since

The big Swiss University network provider has been having severe problems for about 8 hours now --- particularly the cross-atlantic connection seems broken --- Many of you will get R-help or ESS-help E-mails very much delayed. Hope things start working soon by themselves. [for those that are disrupted: When you get this message, things should be back to normal; otherwise you wouldn't have

Well, R ( http://lib.stat.cmu.edu/R/CRAN/ ) has a pictex(..) driver. >>>>> "kjetil" == kjetil halvorsen <kjetil@caoba.entelnet.bo> writes: kjetil> Is there any possibility to write code which ``translates'' kjetil> from splus graphics to latex picture commands? Or somebody has kjetil> written something like that? kjetil> I did

[Same question for max(.), cummin(.) and cummax(.)] In S, S-plus and R, this currently gives NA. I wonder if it wouldn't make more sense to follow common mathematical/logical reasoning here: min { empty set } = +Inf max { empty set } = -Inf (For integers, these would be INT_MAX and INT_MIN, respectively). Maybe this is a real ``first time'': I am proposing a change which

>>>>> "TL" == Thomas Lumley <thomas@biostat.washington.edu> writes: TL> ...... TL> Currently "%*%" doesn't have any help but help TL> requests get routed to Arith, because "%*%" as a regular expression TL> matches "%%". I will add this to the special cases in help(), but TL> should we use fgrep

The reason being a design decision of a while ago that "T" and "F" shouldn't be reserved words in R as they are in S-plus. Hence, T & F are just variables being set to TRUE and FALSE respectively; they *can* be overwritten by the user which is very useful e.g., when you do mydat <- read.table(file, header =TRUE) and the file has variable names "T" or

[CC'ed to R-devel, since it should be of interest to more ..] >>>>> "Guy" == Guy Nason <G.P.Nason@Bristol.ac.uk> writes: Guy> Dear Martin, Hope you are well. I am trying to start to get my Guy> [new] WaveThresh package working for R. Great, thank you! Can you make sure that your Examples (.EX in S syntax; \examples{..} in *.Rd) are directly

R 0.63 only ------------ (0.62 does not have the print-tests.Rout.save against which to diff!) I'd be glad if some of you could help us find out some printing/formatting differences of the same R version on different architectures. I have the suspiscion that the new glibc aka libc-6 (Linux), has changed some of the internal printing/formatting code [fprintf ..]. One consequence is that

As some of you know, we have been thinking of allowing the possibility of a CHOICE of the kind of random number generator (=: RNG) to use in R. The current R-release snapshot even has some code in it; however, this will be changed quite a bit. Here is a kind of informal RFC (request for comments / request for criticism / ..): 1a. With the new scheme, we still want that save(..) &

[forwarded to R-devel, where this really belongs] >>>>> "Samira" == Samira M Ismail <samira@ime.unicamp.br> writes: (to me in a private mail) Samira> We have been trying to install R.0.63 for Unix (SunOS 4.1.4 - Samira> SPARC 20) and we detected the following problem which makes Samira> impossible to run R. We have got the following message:

This was ``accidentally'' only sent to me. But I think the question (and possibly answers) should be relevant to much more people! >> To: maechler at stat.math.ethz.ch >> Subject: manual >> From: Pat Altham <P.M.E.Altham at statslab.cam.ac.uk> >> Date: Thu, 13 Aug 1998 11:34:31 +0100 >> >> Could you kindly email me (or tell me how to obtain)

Looking into several different parts of R../src/library/base/R/*.R has led me to the conclusion that quite a bit of code doubling could be saved by using the following two functions whose naming philosophy is derived from that of NROW() & NCOL(): COLNAMES <- function(x) if(is.null(n <- colnames(x))) paste(seq(length=NCOL(x))) else n ROWNAMES <- function(x)

I've installed hdf5 [library & includes] here locally, last week. [see ?hdf5save in R] There is a remaining compilation / linking problem for me: The hdf5 library uses "compress2" a routine defined in Gnu's zlib, but not available in the zlib that comes with X11R6.3 (which we have installed). Now unfortunately, the final link statement for R (0.65) [for me, with hdf5

In R and S, the general idea is that data.frames must have unique row.names (aka dimnames(.)[[1]]). Several observations / problems (in R *and* S !). [Example code at the end] 1) Both in S and R, data.frame(..) (and e.g., also cbind(<data.frame>, ..) which dispatches to data.frame()) silently drops the whole row.names and replaces it by "1" "2" ...

(I don't have time just now to diagnose & fix..) In R 0.63.3 [both on Solaris and Linux] > example(outer) Error: Couldn't find 'outer' example whereas this worked in 0.63.2. NON-exhaustive `research' [i.e. small sample out of about 1000]: o examples that stopped working (in 0.63.3 and did before) kronecker, outer, vector, Im o Examples working

In current versions of R, pretty(333) gives an infinite loop (due to a silent integer overflow in src/appl/pretty.c). I've looked at this problem and also at what S-plus does, (no code there to inspect, just experiments), and then I have fixed pretty.c. I think that it now behaves much more reasonably (both than before and than S / S-plus). The only problem: pretty(.) is not

[I think Doug Bates has already alluded to this, somewhere..] In R, data.frame( ... ) does not construct row.names whereas in S, it does: R: > data.frame(x=1:2,y=3:4) x y [1,] 1 3 [2,] 2 4 > row.names(data.frame(x=1:2,y=3:4)) NULL S-plus: > data.frame(x=1:2,y=3:4) x y 1 1 3 2 2 4 > row.names(data.frame(x=1:2,y=3:4)) [1] "1" "2"

Maybe embarassing, but I can't quickly find out how to do this: Mix expression() text and regular text __in a variable__ for plotting: I can easily do plot(1,type="n",main=expression(paste("Plot of ", x ^ alpha, "; ", alpha==2.3) However, if alpha is really just in a variable, I don't know what to do alpha <- 2.3 ch.a <- format(alpha) and now

Maybe embarassing, but I can't quickly find out how to do this: Mix expression() text and regular text __in a variable__ for plotting: I can easily do plot(1,type="n",main=expression(paste("Plot of ", x ^ alpha, "; ", alpha==2.3) However, if alpha is really just in a variable, I don't know what to do alpha <- 2.3 ch.a <- format(alpha) and now