On Wed, 21 Mar 2012, Vitalie Spinu wrote:
Vitalie Spinu
on Wed, 21 Mar 2012 14:39:52 +0100 wrote:
on Wed, 21 Mar 2012 07:46:21 -0500 wrote:
>> I can't reproduce this in either 2.14.1 or R-devel.
> Hm .. I cannot reproduce it, nor with the latest R-devel, nor with 2.14.2
> anymore. Som
Vitalie Spinu
on Wed, 21 Mar 2012 14:39:52 +0100 wrote:
on Wed, 21 Mar 2012 07:46:21 -0500 wrote:
>> I can't reproduce this in either 2.14.1 or R-devel.
> Hm .. I cannot reproduce it, nor with the latest R-devel, nor with 2.14.2
> anymore. Some local glitch or somethi
on Wed, 21 Mar 2012 07:46:21 -0500 wrote:
> I can't reproduce this in either 2.14.1 or R-devel.
Hm .. I cannot reproduce it, nor with the latest R-devel, nor with 2.14.2
anymore. Some local glitch or something ...
Vitalie.
__
R-devel@r-pr
I can't reproduce this in either 2.14.1 or R-devel.
luke
On Wed, 21 Mar 2012, Vitalie Spinu wrote:
Hi,
Browser doesn't work properly with the compiler enabled. It might be
intended behavior, but it's not documented.
compiler::enableJIT(1)
foo <- function(){
browser()
cat("here\n")
}
FYI
https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14594
On 03/21/2012 10:19 AM, Vitalie Spinu wrote:
Hi,
Browser doesn't work properly with the compiler enabled. It might be
intended behavior, but it's not documented.
compiler::enableJIT(1)
foo<- function(){
browser()
cat(
Hi,
Browser doesn't work properly with the compiler enabled. It might be
intended behavior, but it's not documented.
compiler::enableJIT(1)
foo <- function(){
browser()
cat("here\n")
}
Browser doesn't stop, and I am getting:
> foo()
Called from: foo()
Browse[1]> here
>
Thanks,
V
