similar to: save/load hooks

It appears that "break" will break from the outermost enclosing loop not the innermost loop. Is it a bug or language feature? Tim -- Timothy H. Keitt National Center for Ecological Analysis and Synthesis 735 State Street, Suite 300, Santa Barbara, CA 93101 Phone: 805-892-2519, FAX: 805-892-2510 http://www.nceas.ucsb.edu/~keitt/

If you have had problems with the latest configure script in RPgSQL, please try the version attached to this message. Let me know if you have any problems. Thanks. Tim -- Timothy H. Keitt National Center for Ecological Analysis and Synthesis 735 State Street, Suite 300, Santa Barbara, CA 93101 Phone: 805-892-2519, FAX: 805-892-2510 http://www.nceas.ucsb.edu/~keitt/ -------------- next part

If you have had problems with the latest configure script in RPgSQL, please try the version attached to this message. Let me know if you have any problems. Thanks. Tim -- Timothy H. Keitt National Center for Ecological Analysis and Synthesis 735 State Street, Suite 300, Santa Barbara, CA 93101 Phone: 805-892-2519, FAX: 805-892-2510 http://www.nceas.ucsb.edu/~keitt/ -------------- next part

The current INSTALL script calls ./configure if it exists when installing packages, but does not check the return value from configure. I have my configure script abort under certain conditions and it would be nice if the INSTALL script would stop at that point. Also, is there an autoconf macro for testing for gnu make? Tim -- Timothy H. Keitt National Center for Ecological Analysis and

A preliminary release of my postgres package for R is at http://www.nceas.ucsb.edu/~keitt/R/postgres.tgz It allows one to read and write data frames to and from a postgres database, execute queries and has an experimental "proxy" interface that allows you to access postgres tables using the standard, local data frame model. All accesses to the data frame generate the appropriate

A preliminary release of my postgres package for R is at http://www.nceas.ucsb.edu/~keitt/R/postgres.tgz It allows one to read and write data frames to and from a postgres database, execute queries and has an experimental "proxy" interface that allows you to access postgres tables using the standard, local data frame model. All accesses to the data frame generate the appropriate

Congrats on the new release. The new package management tools are great! A couple of quick comments: 1) it might be nice to add an optional "Autoloads:" field to the description (the package does not depend on these other packages, but will autoload them if certain functions are called). 2) on page 3 of the R-exts document, it says to set PKG_* flags in 'Makeconf'; I think

I've been putting together a package that defined generic methods for database access. The packages is called "Rdbi." It borrows as much as possible from existing database packages / proposals. I'd like to start a discussion about the proposed interface. Here's what I've come up with so far: # # Rdbi: connectionMethods.R # dbConnect <- function(dbObj, ...)

Hello R-users, during one of my analyses that involve a SVD, I get the following error message: Error in La.svd(x, nu, nv, method) : error code 1 from Lapack routine dgesdd With a search on the R web site, I only found references to error codes 17 and 3 for this particular routine. I also found the Lapack web site, but could not find a list of the possible error messages. If somebody knows what

I see some code in R to attach finalizers to external pointer references (Register[C]Finalizer). Anyone have an example of how to code the finalizer? R_RegisterCFinalizer accepts a C function, but I can't see how to get it to operate on the pointer, since the pointer is not passed to the function when its called. RegisterFinalizer takes an R closure, but how is it called from R (tried

Hallo, I am a newbie to R and desperatley seeking some material about fractal geometry. I found the great library on wavelet analysis of images and I'm now also keen on finding a similar package for calculating fractal parameters for given images. Does anybody know something about such a package? Every hint is greatly appreciated!! I searched already the database, but did not find anything

None of this is greatly important but might be a bit useful to someone. BTW, I have 0.99a installed, it compiled without a problem. I've discovered most of the plotting facilities including the legend() function and the various text annotations, this is nice an convenient and flexible enough to do most things. One thing that I must say is that the help pages on plot() and plot.default()

I'm doing convolutions in the frequency domain and need to know the layout of the Fourier modes returned by fft. (This is leading up to a more involved question about moment generating functions, but I need to know if I've got this part correct first.) I think in 1D the pattern is: 0 1 2 3 -2 1 (even) 0 1 2 3 -3 2 1 (odd) In 2D is it simply (for a square matrix): 0 1 2 -1 (horizontal)

Hello: I would like to superimpose vector polygons (state outlines) from a Shape file on top of a satellite image, imported into a SpatialGridDataFrame from GEOTIFF via gdal_translate and readGDAL. When I plot polygon and point shape files in R, into SpatialPointDataFrame and SpatialPolygonDataFrame, the two feature sets line up geographically, so it seems logical that a SpatialGridDataFrame

I'm revisiting the R/S DBI package and was wondering if there is any plan to implement package name spaces in R/S. I've taken to the habit of prepending a few characters to function names in packages to avoid collisions, e.g., dbConnect(). An alternative would be DBI::connect() (s/::/preferred/) which in some ways I find more pleasing. Not having thought about it in detail, it seems pretty

Full_Name: Tim Keitt Version: 1.4 OS: Linux Submission from: (NULL) (129.49.19.70) I think this code in 'ts' is incorrect: if (is.matrix(data) || is.data.frame(data)) { nseries <- ncol(data) ndata <- nrow(data) dimnames(data) <- list(NULL, names) } since > x <- data.frame(matrix(rnorm(100),ncol=10)) > names(x) [1] "X1"

I seem to remember something about an "internal" keyword for R doc files. How do we use it? Tim -- Timothy H. Keitt Department of Ecology and Evolution State University of New York at Stony Brook Stony Brook, New York 11794 USA Phone: 631-632-1101, FAX: 631-632-7626 http://life.bio.sunysb.edu/ee/keitt/ -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

Its not clear from the documentation whether one should do \keyword[key1, key2} or \keyword{key1} \keyword{key2} in .Rd files. I believe the latter is correct. (At least 'R CMD check' complains when given the first version.) It would help to make this explicit in the R extension writing docs. Tim -- Timothy H. Keitt Department of Ecology and Evolution State University of New

I'm curious if any of the core R developers have considered the possibility of hosting R (v2?) on the parrot common runtime environment. Perl6 will generate byte-code for parrot, as will some future version of python. I can imagine both drawbacks and advantages. Some advantages would be fast byte-code execution and freely mixing perl, python and R modules. Anyone looked into this? Tim

I have an application where I need to preserve object attributes across calls to 'lapply'. The current definition is: lapply <- function (X, FUN, ...) { FUN <- match.fun(FUN) if (!is.list(X)) X <- as.list(X) rval <- .Internal(lapply(X, FUN)) names(rval) <- names(X) return(rval) } Would it make sense to replace names(rval) <- names(X)