similar to: lambda error update

Matthew Wiener <mcw@ln.nimh.nih.gov> writes: > > parameters (xxdefun in gram.y calls lang4). The arg count got changed > > from 0.64.2 to 0.65.0 (from 3 to 4) to accommodate the stored source > > attribute. I suppose that a function stored in a saved workspace might > > cause some kind of mess when restored. > > > > If I understand this correctly, it

I originally posted this to R-help, but here is probably a better place. I have a rather complex routine which works great in R. Then I bootstrap it. After running a few minutes it typically segfaults, though it happens very randomly. This happens w/ 1.9.0 and 1.9.1 on Fedora1 and a Scyld (RH7.3) system. Traces always point back to routines in src/main/memory.c, though often not the same

Hi I seem to have run into a situation where I have more than 3 arguments to pass to a function from C. the following functions help me build an expression for evaluation: lang lang2 lang3 lang4 What should one do if there are more arguments than lang4 can handle? Regards Abhijit Bera [[alternative HTML version deleted]]

I'm trying to get a reference to this object in C SWX.RET[1:6,c("SBI,"SPI","SII")] While i am able to access and use a plain SWX.RET object, I'm getting confused on how to create an object with the array subscripts like above. Here is what I tried to do. It doesn't work because "[" is obviously not an operation or function on SWX.RET. So how do I

Hello, Using R-devel (rev 53950), I get inconsistent results with as.environment( VECSXP ) when gctorture is on. Consider: a <- list( aa = rnorm, bb = runif ) gctorture(TRUE) as.environment( a ) The last line sometimes produces the correct environment, but sometimes I get errors. Here are the three situations: # good > as.environment( a ) <environment: 0x100b1c978> # not good

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Hi. I'm having a problem with disappearing comments when I transfer files (entire .RData files) from one machine to another, and I'm not sure whether it's an R problem or an ESS problem. Since ESS seems more likely, I'm trying this list first. (However, it seems to me this problem only showed up when I upgraded to R-0.65.0 or R-0.65.1.) Functions originally shows up fine -- if

Hi I'm trying to implement something similar to the following R snippet using C. I seem to have hit the wall on accessing class slots using C. library(fPortfolio) lppData <- 100 * LPP2005.RET[, 1:6] ewSpec <- portfolioSpec() nAssets <- ncol(lppData) setWeights(ewSpec) <- rep(1/nAssets, times = nAssets) ewPortfolio <- feasiblePortfolio( data = lppData, spec = ewSpec,

Hi, all. The following does not behave as I think it should, and as it seems to me it has in the past (although I can't check this easily). I know it happens in both R-0.64.2 and R-0.65.0 on an old Power Computing running Linux-PPC 1999, and in R-0.64.2 on an SGI running Irix 6.5. Try the following: t1 <- data.frame(matrix(rnorm(16), nc=4)) > t1 X1 X2 X3 X4 1 -0.7206945

I am occasional getting "Segmentation Fault - core dumped" in R 0.62.3 (I think more often then I did in 0.62.2). I have not been able to do this in any reliably reproducible way yet, but thought I would mention the problem in case some else can isolate it. Paul Gilbert -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

The following commands illustrate a problem with graphing relatively large data sets using the "line" option to plot: temp <- runif(200000) # or whatever other numbers you like; # same thing happens with a sine wave plot(1:200000, temp) # everything fine plot(1:200000, temp, type="l") # data gets cut off The number of points isn't crucial. The cutoff point

Hello, all. I have a somewhat embarrassing error, in that I cannot reliably reproduce it. I have sporadically experienced the error both on an SGI machine running Irix 6.5 and on a LinuxPPC machine. I have only seen this error using version 0.65.0. (I've been using versions since 0.61 or so.) The error message is in the subject line. Here's the traceback from the most recent

Hi, all. I'm not sure whether this is a problem with ESS or R (or even a feature I don't understand!). Say I've got a function named f.count.these.patterns (as I do -- I'm using actual names in case they're somehow important). I previously had a version called f.count.these.patterns.3, but discarded it because it was worse. So the function is no longer there. If I create a

Hi , I am asking too many questions , sorry for that . I am creating a data frame in C itself , reading a table . The data frame calling code looks like this ====================================== *PROTECT(dfm=lang2(install("data.frame"),df));* *SEXP res = PROTECT(eval(dfm,R_GlobalEnv));* UNPROTECT(2); return res; ================================== It works fine , now the problem

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

I have a package that solves systems of ordinary differential equations coded as an R function (odesolve, on CRAN). The function is passed to R code, and c and Fortran code called by it uses lang4() and eval() to evaluate the R function inside a compiled c function to use in a compiled ODE solver. This works quite well, but can be slow. I'd like to be able to supply the name of a compiled

Full_Name: Thomas Langhans Version: 0.65 OS: Solaris 7 Submission from: (NULL) (129.217.131.31) I tried to install the package "leap" on our Sun Enterprise 400 running Solaris 7, but it fails: cause the g77 doesn't compiles the fortran-sources properly, I translated them with f2c to c-source. Running R INSTALL produces the following message: Installing package `leaps' ...

Hi, all. In trying to compile R v.0.90 on an alpha running Red Hat Linux 6.0, I'm getting the following error: make[3]: Entering directory `/home/mcw/alpha-R/R-0.90.0/src/appl' gcc -I. -I../include -I../../src/include -DHAVE_CONFIG_H -mieee -g -O2 -c cpoly.c -o cpoly.o /tmp/ccPjZNwd.s: Assembler messages: /tmp/ccPjZNwd.s:312: Error: unknown opcode `sqrttsu' /tmp/ccPjZNwd.s:2631: