similar to: environment or other technique to isolate some private working information

Hi R-devel, The following code: all.equal(baseenv(), baseenv()) gives the error when run in a clean R session with latest R-devel (r66650): kevin:~$ R --vanilla --slave -e "all.equal(baseenv(), baseenv())" Error in all.equal.envRefClass(target[[i]], current[[i]], check.attributes = check.attributes, : attempt to apply non-function Calls: all.equal ...

On Fri, Mar 4, 2016 at 11:28 AM, Tilmann Scheller <tilmann at osg.samsung.com> wrote: > Hi Sedat, > > On 03/03/2016 08:09 AM, Sedat Dilek via llvm-dev wrote: >> >> It might be that a CLANG generated with LTO/PGO speeds up the build. >> Can you confirm this? > > Yes, a Clang host compiler built with LTO or PGO is generally faster than an > -O3 build. >

I've just committed some changes to R-devel which affect environments. Specifically: - using NULL as an environment is now deprecated: use baseenv() instead. (baseenv() is already available in R 2.2.0, where it returns NULL. For most purposes it retains the same meaning in R-devel.) If you do use NULL, it will be converted to baseenv(), and a warning printed. For example: > f

Hi, I am trying to run many different regressions using a FOR Loop. The input data that is read into R has the following variables · Volume · Price1 · Price2 · Price3 · Price4 · Price5 · Trend · Seasonality I want to run 5 regressions, with the Volume as an dependent variable and Price, Trend & Seasonality as

Hello, I am trying to get the trace by running my sample program using llvm. I was referring following link for lli: http://llvm.org/releases/1.0/docs/CommandGuide/lli.html after that I installed llvm and llvm-gcc. Here is the version detail: tushar at tushar-mehta:~/NUS/os_project/tryout$ lli -version Low Level Virtual Machine (http://llvm.org/): llvm version 2.8 (Ubuntu 2.8-0ubuntu1)

eapply() works on most environments, but not on baseenv(). For example, > x <- 1 > eapply(globalenv(), function(x) x) $x [1] 1 > eapply(baseenv(), function(x) x) list() I'm probably not going to have time to work on this before 2.3.0, but I don't think it's really urgent; if no one else fixes it first I'll do it after the release. Duncan Murdoch

I understand why the following happens ($.proto delegates to get, which ascends the parent hierarchy up to globalenv()), but I still find it anti-intuitive: > z <- 1 > y <- proto(a=2) > y$z [1] 1 Although this is well-documented behavior; wouldn't it uphold the principle of least surprise to inherit instead from baseenv() or emptyenv()? (See attached patch.) Spurious

https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16660 Here is the bug, which R.home may generate a path contains a whitespace. this will cause Rcpp failed executing sourceCpp > sourceCpp("b:/2018-12-14/src/18020/MCMC.cpp") Error in system(cmd, intern = !showOutput) : 'D:/Program' not found Error in system(cmd, ignore.stderr = TRUE, intern = TRUE) :

Thank you for your suggestion. I do know how to work around the issue. I usually build a fresh environment as a child of base-environment and then insurt the weights there. I was just trying to provide an example of the issue. emptyenv() can not be used, as it is needed for the eval (errors out even if weights are not used with "could not find function list"). For some applications

Buffer overflow detect in FC6-x86_64, see down. Juan. R version 2.4.0 (2006-10-03) Copyright (C) 2006 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R ? um software livre e vem sem GARANTIA ALGUMA. Voc? pode redistribu?-lo sob certas circunst?ncias. Digite 'license()' ou 'licence()' para detalhes de distribui??o. R ? um projeto colaborativo com muitos

Duncan, I agree completely with "don't use attach"; if I could get all the users of the survival package to agree as well the problem in question would go away :-) I'm thinking about ways to add more effective error surveillance. Your suggestion was not horribly complex and I'll look into it further. My first foray failed because what I want (I think) is the

# R for Windows will not send your bug report automatically. # Please copy the bug report (after finishing it) to # your favorite email program and send it to # # r-bugs at r-project.org # ###################################################### Dare I say the word: bug. It looks to me like a bug in conficts(). The use of seq_along in this line in base::conflicts + for (i in

Given the extremely simple package at https://github.com/jimhester/testUnload, which includes only one S3 method 'print.object' the following code produces a lazy load error from a new R session (R-devel r69801) install.packages("testUnload", repos = NULL) library("testUnload") unloadNamespace("testUnload") install.packages("testUnload", repos =

On 10/08/2020 1:42 p.m., John Mount wrote: > I wish I had started with "I am disappointed that lm() doesn't continue its search for weights into the calling environment" or "the fact that lm() looks only in the formula environment and data frame for weights doesn't seem consistent with how other values are treated." Normally searching is done automatically by

I've been using Rterm with ESS to run R for some time. Recently I've experienced lockups when displaying graphics; the first display seems to work, but then refuses to respond and must be killed with dev.off(). Rgui has no problems. I've tried eliminating all other processes that might cause conflicts, to no avail. I'm using win XP and R 2.9.0. Here's a transcript using rterm:

1. I did not attempt to sort through your voluminous code. But I suspect you are trying to reinvent wheels. 2. I don't understand this: "I've failed to find a solution after much searching of various R related forums." A web search on "error handling in R" **immediately** brought up ?tryCatch, which I think is what you want. If not, you should probably explain why it

I?m wondering which is the most efficient (time, than memory usage) way to obtain a multivariate time series object from a data frame (the easiest data structure to get data from a database trough RODBC). I have a starting point using timeSeries or xts library (these libraries can handle time zones), below you can find code to test. Merging parallelization (cbind) is something I?m thinking at

You can capture warnings by using withCallingHandlers. Here is an example, its help file has more information. dataList <- list( A = data.frame(y=c(TRUE,TRUE,TRUE,FALSE,FALSE), x=1:5), B = data.frame(y=c(TRUE,TRUE,FALSE,TRUE,FALSE), x=1:5), C = data.frame(y=c(FALSE,FALSE,TRUE,TRUE,TRUE), x=1:5)) withWarnings <- function(expr) { .warnings <- NULL # warning handler will

tryCatch() is good for catching errors but not so good for warnings, as it does not let you resume evaluating the expression that emitted the warning. withCallingHandlers(), with its companion invokeRestart(), lets you collect the warnings while letting the evaluation run to completion. Bill Dunlap TIBCO Software wdunlap tibco.com On Tue, Mar 6, 2018 at 2:45 PM, Bert Gunter <bgunter.4567 at

Gentlemen, Did tryout "CONNECTEDLINE" function, was exactly what I have been looking for. But there are at least one thing I cant figure out. Did a very simple and "stupid" extension 0317998955 and ran a test. My phone (0317998975) dials 955, the display on my phone changes from "955" to "Connected Line 955" when my call is answered, shouldn't the