> Peter Bosa
> on Tue, 22 Aug 2017 14:39:50 + writes:
> Hello, I've noticed the following error using repeat{} / break in R 3.4.1
running on Windows 10 and Windows Server 2008 (both 64-bit environments).
> When running a repeat function, the break command causes an error
> Martin Maechler
> on Wed, 23 Aug 2017 09:10:20 +0200 writes:
> Peter Bosa
> on Tue, 22 Aug 2017 14:39:50 + writes:
>> Hello, I've noticed the following error using repeat{} / break in R
3.4.1 running on Windows 10 and Windows Server 2008 (both 64-bit environme
I don't think that's a bug. source() uses eval(), and eval() creates a
new function-like context frame. In a way expecting `break` to work
inside source() is like expecting `break` to cross stack frames:
my_break <- function() break
repeat(my_break())
Lionel
> On 23 août 2017, at 09:17,
It is a bug in the byte-code compiler. I will fix
Tomas
On 08/23/2017 09:22 AM, Lionel Henry wrote:
I don't think that's a bug. source() uses eval(), and eval() creates a
new function-like context frame. In a way expecting `break` to work
inside source() is like expecting `break` to cross stack
oops, I should have tried it:
expr <- quote(break)
repeat(eval(expr))
So eval() has hybrid semantics where `break` has more reach than
return(), weird.
expr <- quote(return())
repeat(eval(expr)) # infloop
Lionel
> On 23 août 2017, at 09:24, Tomas Kalibera wrote:
>
> It is
Fixed in 73112.
If you needed to run this code in unpatched versions of R, you can
disable the problematic compiler optimization in the loop for instance
by adding "eval(NULL)" to the body of the loop. However, please do not
forget to remove this for future versions of R and specifically do no
return can be used to set the return value of an expression evaluated by
"eval"
expr <- quote(if (x) return(1) else return(2))
x <- FALSE
eval(expr) #2
Tomas
On 08/23/2017 09:46 AM, Lionel Henry wrote:
oops, I should have tried it:
expr <- quote(break)
repeat(eval(expr))
So eva
Dear list, R-core,
The documentation of stats::stl explicitly refers to the paper by
Cleveland[1] to explain the parameters. However, the description is
confusing, with two descriptions seeming to refer to the same parameter in
the paper.
s.window: [...] the loess window for seasonal extraction,
Hi,
I have sent this message to this list the July, 7th. It was about a
problem in MASS package.
Until now there is no change in the devel version.
As the problem occurs in a package and not in the R-core, I don't know
if the message should have been sent here. Anyway, I have added a copy
to P
Thank you, Gentlemen...much appreciated!
peter bosa
metro
transportation research and modeling services
600 ne grand ave
portland, or 97232
peter.b...@oregonmetro.gov
503.797.1771
metro | making a great place
www.oregonmetro.gov
10 matches
Mail list logo
