-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct .Call() function signatures #317
Comments
@eddelbuettel My preliminary checks suggest this is going to affect RcppXts. My understanding is that I need to do one of two things to
What are your thoughts/preferences? |
To clarify, not registering a function will not solve the problem. If a function is not registered, but is called via |
I got a similar email from Tomas and already fixed it (in
Haven't looked at Edited again, adding an important not above |
Yes, functions for use with |
Thank you both for your input! It looks like I only need to stop registering those functions for josh@thinkpad: ~/git/xts/R (master)
> grep -E "\.Call\(.(isXts|do_merge_xts)" *
That also means RcppXts should be okay, since the function signatures do not need to change. |
All C functions called via
.Call()
must returnSEXP
and have allSEXP
arguments. This is not true fordo_merge_xts()
andisXts()
. This may change the API, and impact RcppXts. Need to confirm.Via email from @kalibera:
The text was updated successfully, but these errors were encountered: