similar to: Strange parse behavior (PR#8815)

Displaying 20 results from an estimated 20000 matches similar to: "Strange parse behavior (PR#8815)"

2006 Apr 27
0
Strange parse behavior
Hi, I discovered the following strange behavior in parse () on syntactically incorrect statements. This is on R 2.3.0 (linux). It may or may not have been present earlier than 2.3.0, but I only discovered it recently. I can see no mention of it in the NEWS file from trunk. Consider these statements (the output I get is shown commented below each statement): bad.syntax <- ")\nprint
2020 May 24
1
Surpising behavior when using an active binding as loop index in R 4.0.0
A shorter reproducible example: example(makeActiveBinding) for (fred in 1:3) { 0 } ls() Both problems go away if you first do compiler::enableJIT(2) So looks like a bug in compiling the for loop. -Deepayan On Sat, May 23, 2020 at 5:45 PM Thomas Friedrichsmeier via R-devel <r-devel at r-project.org> wrote: > > Possibly just a symptom of the earlier behavior, but I'll amend my
2007 Feb 01
0
Fwd: Re: read.spss and encodings
--- John Kane <jrkrideau at yahoo.ca> wrote: > Date: Thu, 1 Feb 2007 09:07:11 -0500 (EST) > From: John Kane <jrkrideau at yahoo.ca> > Subject: Re: [R] read.spss and encodings > To: Thomas Friedrichsmeier > <thomas.friedrichsmeier at ruhr-uni-bochum.de> > > Hi Thomas, > > I am using R 2.4.1 on WindowsXP and I don't seem to > be > having any
2006 Oct 06
1
operator :: and symbols not in the namespace of a package with a namespace (PR#9279)
Full_Name: Thomas Friedrichsmeier Version: 2.4.0 OS: GNU/Linux Submission from: (NULL) (84.61.116.51) Since R 2.4.0, operator "::" also returns objects in the package environment, if the package does not have a namespace. This is a very welcome addition. Additional wish: If a package has a namespace, but does not place all symbols in that namespace, lookup will still fail. For example
2006 Apr 10
2
install.packages on unix / su (PR#8760)
Full_Name: Thomas Friedrichsmeier Version: R 2.2.1 OS: Debian / Linux Submission from: (NULL) (84.60.123.243) Wishlist item: There is a small problem using intall.packages() (and update.packages()): Typically I want to install packages for system-wide use, not in a user directory. Obviously this does not work without superuser rights. What I would like to be able to do is to specify a
2020 May 23
0
Surpising behavior when using an active binding as loop index in R 4.0.0
Possibly just a symptom of the earlier behavior, but I'll amend my example, below, with an even more disturbing observation: Am Sat, 23 May 2020 13:19:24 +0200 schrieb Thomas Friedrichsmeier via R-devel <r-devel at r-project.org>: [...] > Consider the code below: > > makeActiveBinding("i", > function(value) { > if (missing(value)) { > x > } else {
2009 Jan 08
0
Parse-Error creates strange function calls (completely different (PR#13438)
This is not a bug. Read ?paste: if you give it a vector, it will give you a vector result. That's what you're seeing. Duncan Murdoch oliver at first.in-berlin.de wrote: > Full_Name: Oliver Bandel > Version: R version 2.7.1 (2008-06-23) > OS: Linux (Debian Lenny) > Submission from: (NULL) (88.73.82.147) > > > Hello, > > I have written a small R-script. >
2008 Mar 13
0
new version of minpack.lm
The package minpack.lm allows nonlinear regression problems to be addressed with a modification of the Levenberg-Marquardt algorithm based on the implementation of 'lmder' and 'lmdif' in MINPACK. Version 1.0-8 of the package is now available on CRAN. Changes in version 1.0-8 include: o possibility to obtain standard error estimates on the parameters via new methods for
2008 Mar 13
0
new version of minpack.lm
The package minpack.lm allows nonlinear regression problems to be addressed with a modification of the Levenberg-Marquardt algorithm based on the implementation of 'lmder' and 'lmdif' in MINPACK. Version 1.0-8 of the package is now available on CRAN. Changes in version 1.0-8 include: o possibility to obtain standard error estimates on the parameters via new methods for
2009 Jan 07
1
Parse-Error creates strange function calls (completely different printouts) (PR#13436)
Full_Name: Oliver Bandel Version: R version 2.7.1 (2008-06-23) OS: Linux (Debian Lenny) Submission from: (NULL) (88.73.82.147) Hello, I have written a small R-script. When I inserted one line of code, the behaviour was completely different! Instead of just printing one line more to the output, the complete call of the function in which this line was added, is different, and instead of one such
2020 May 24
0
Fwd: RKWard and R 4.0.0 - Important bug and workaround
Dear all, as I am providing rkward backports for Debian testing and stable on CRAN, I am forwarding this notice by the main developer. Meanwhile, it has been communicated that R 4.0.1 will be released on June 6. Cheers, Johannes ---------- Weitergeleitete Nachricht ---------- Betreff: RKWard and R 4.0.0 - Important bug and workaround Datum: Sonntag, 24. Mai 2020, 10:14:17 CEST Von:
2006 Nov 11
2
Strange yum behavior
Hello, 'yum search R' returns an impossibly-long list. So I tried 'yum search R.x86_64' and 'yum search R-2.3.0' and few others to no avail. (Google revealed that R package does exist in kbsingh repository.) However, 'yum install R' did offer to install the correct package. Can someone enlighten me as to why did the searches failed or generated a hugh list
2011 Mar 15
1
Problem with nls.lm function of minpack.lm package.
Dear R useRs, I have a problem with nls.lm function of minpackl.lm package. I need to fit the Van Genuchten Model to a set of data of Theta and hydraulic conductivity with nls.lm function of minpack.lm package. For the first fit, the parameter estimates keep changing even after 1000 iterations (Th) and I have a following error message for fit of hydraulic conductivity (k); Reason for
2003 Dec 25
0
Re: if .. else parse error {was "Sweave question"} (fwd)
Dear All, Thanks to all that took the time to respond to my questions (included at the bottom). Martin Maechler was nice enough to give me a detailed explanation which he suggested i forward. The confusion arose because if(exists("x")) plot(x,x) else{ plot(1,1,type="n");text(1,1,"data not available.\n")} gave me an error when used as a chunk in a Sweave
2007 Jan 17
2
R_ParseVector API change
Dear R developers, just a quick question: I noted that R_ParseVector () has gained an additional parameter (since SVN rev. 39999). Since R_ParseVector () is part of the public API, I'm wondering, whether this API change was intentional or not. Either way is fine with me, but in order to make sure the next release of RKWard will be compilable with R 2.5.0, I'd like to make sure,
2007 Mar 29
1
small bug in ansari.test
The help page for ansari.test() says (emphasis added): By default (if exact is not specified), an exact p-value is computed if both samples contain less than 50 finite values **and there are no ties**. Otherwise, a normal approximation is used. However, this does not appear to be the case in R 2.4.1 or R 2.5.0. In fact, even example(ansari.test) produces a warning Warning message:
2006 Jun 11
0
qunif() behavior with Inf arguments (PR#8958)
Full_Name: Rob Carnell Version: 2.3.0 OS: Windows XP sp 2 Submission from: (NULL) (131.167.72.220) Thank you for all you work on R project! I noticed the following behavior today. It is what I believe to be an inconsistency. > qunif(.5, 0, Inf) [1] Inf > qunif(.5, -Inf, 1) [1] NaN Warning message: NaNs produced in: qunif(p, min, max, lower.tail, log.p) I believe they should yield the
2009 Feb 12
1
Using nls or nls.lm with a simulation output
We would like to fit parameters using a simulation with stochastic processes as theoretical values. We generate a simple exemple with nls.lm to see the logic and the problem: First without stochasticity (it is a dummy example, the fited value is simple the mean of a set of 10 numbers): #Ten numbers x <- 1:10 #Generate 10 Gaussian random number with mean=3 sd=1 simy <- rnorm(length(x),
2006 Sep 30
1
Strange behaviour of the [[ operator (PR#9263)
On 9/29/2006 9:06 PM, Herve Pages wrote: > Hi, > > This looks like a bug: > > > a <- list(b=5) > > a[['b']] > [1] 5 > > a[[t<-'b']] > > Nothing gets printed! > > I need to use parenthesis to see the expected result: > > > a[[(t<-'b')]] > [1] 5 Yes, I agree it looks like a bug,
2002 Nov 08
2
behavior of =
I probably didn't follow the discussion of allowing "=" as an assignment operator closely enough, but I was a little bit horrified to discover today (using 1.6.0; I haven't upgraded to 1.6.1 yet) that x <- runif(20) y <- 1:20 y[x=min(x)] gives numeric(0) (because min(x) is non-integer). x <- sample(1:20,20,TRUE) y[x=min(x)] is even worse -- it gives the