Skip to content
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

Use STRICT_R_HEADERS in Rcpp.h #613

Closed
wants to merge 1 commit into from
Closed

Use STRICT_R_HEADERS in Rcpp.h #613

wants to merge 1 commit into from

Conversation

jeroen
Copy link
Contributor

@jeroen jeroen commented Dec 14, 2016

This is only a simple suggestion. It defines STRICT_R_HEADERS inside Rcpp.h to prevent issues like #612 in the future.

I would be much in favor of setting STRICT_R_HEADERS unconditionally, but that might break an existing package or two (or perhaps not).

@eddelbuettel
Copy link
Member

Please don't do pull requests before discussion.

I though of this as soon as you raised the issue. But we were just burned somewhere else by another package doing something 'too widely' in its header so I am against unconditional inclusion.

@jeroen
Copy link
Contributor Author

jeroen commented Dec 14, 2016

Well the PR is not unconditionally. If it was not previously defined, it will undefine it at the end. So STRICT_R_HEADERS is only defined inside Rcpp.h.

@eddelbuettel
Copy link
Member

eddelbuettel commented Dec 14, 2016

Well but as the proponent of the proposal, it is would appear to be your responsibility to assess how widely it affects client packages. For that you would need to run reverse depends.

If it were unconditional, it wouldn't fail Travis either. So you have your counter proof right here, no? (Though it may pass once we clean up sample.h.)

Would you be terribly upset if I closed this here and we carry on over in #614?

@jeroen
Copy link
Contributor Author

jeroen commented Dec 14, 2016

It fails because of #612 which is precisely the goal of the PR. Once the bug has been fixed it will no longer fail. But feel free to close I was just trying to discuss this suggestion here. You can move it to another issue.

@eddelbuettel
Copy link
Member

I do hate red in Travis so submitting this now before we got to the fix needed to pass strikes me as ... suboptimal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants