From tomas.kalibera at gmail.com  Thu Jul  6 18:29:07 2017
From: tomas.kalibera at gmail.com (Tomas Kalibera)
Date: Thu, 6 Jul 2017 18:29:07 +0200
Subject: [Rd] [Bug Fix] Default values not applied to ... arguments
In-Reply-To: <8b83c113-8ec1-bf78-17f5-66682b798475@asilaycomputing.com>
References: <8b83c113-8ec1-bf78-17f5-66682b798475@asilaycomputing.com>
Message-ID: <0555003e-e7fe-9b3d-def7-852a0644ebdc@gmail.com>


Thanks for the report, I've fixed 15199 in the AST interpreter in 72664, 
I will fix it in the byte-code interpreter as well.

If you ever needed to disable the JIT, there is API for that, see 
?compiler. Note though that by disabling the JIT you won't disable the 
byte-code interpreter, because code also gets compiled when packages are 
installed or when the compiler is invoked explicitly.

Best,
Tomas

On 07/06/2017 04:40 PM, Sahil Kang wrote:
> Hi Duncan, Martin
>
> Here's a small patch that fixes bug 15199 reported at:
> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15199
>
> I was able to reproduce the bug as Duncan had outlined just fine, but 
> I did notice that when we debug(f), the problem went away.
> I later realized that f(1,,3) behaved correctly the first time it was 
> executed, but misbehaved as documented on subsequent calls.
> This narrowed the problem down to the byte-compilation that occurs on 
> subsequent function calls.
>
> This patch prevents byte-compilation on closure objects.
> Although it's a less than ideal solution, this patch fixes the bug at 
> least until the underlying byte-compilation issue can be found (I'm 
> currently scrutinizing the promiseArgs function at eval.c:2771).
>
> Thanks,
> Sahil
>
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



	[[alternative HTML version deleted]]



[Rd] [Bug Fix] Default values not applied to ... arguments
Tomas Kalibera