The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with
HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now
fixed in R-devel - please check if that works for you.
Thanks,
Simon
> On Dec 26, 2016, at 11:25 PM, Laurent Gautier wrote:
>
> Hi,
>
Thanks for looking at it. Having HAVE_UINTPTR_T defined in Rconfig.h
should fix the issue. Will the fix make it to R-3.3.3 (if that point
release is planned, or R-3.3.2-patched), or will it only be with R-3.4 ?
L.
PS: I am forwarding a thank you note to the reporter of the problem on the
rpy2 i
> Hi there,
> Any update on this?
> Should I create bugzilla ticket and submit patch?
> Regards
> Jan Gorecki
Hi Jan,
Why should we care that the do.NULL = FALSE case is slower?
After all do.NULL = TRUE is the default.
In other words, where are use cases where it is problematic that
do.NULL =
> Martin Maechler
> on Thu, 22 Dec 2016 10:24:43 +0100 writes:
> Florent Angly
> on Tue, 20 Dec 2016 13:42:37 +0100 writes:
>> Hi all,
>> I believe there is an issue with passing NULL to the function I().
>> class(NULL) # "NULL" (as expected)
>> print(
