8000 Non-API calls · Issue #762 · r-lidar/lidR · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Non-API calls #762

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.

Sign up for GitHub

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

Jump to bottom
Open
Jean-Romain opened this issue Jun 22, 2024 · 3 comments
Open

Non-API calls #762

Jean-Romain opened this issue Jun 22, 2024 · 3 comments
Assignees
@Jean-Romain
Labels
CRAN A change that is required by the CRAN

Comments

@Jean-Romain
Copy link
Collaborator
Jean-Romain commented Jun 22, 2024 •
edited
Loading

New CRAN policy check

Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

Easy:

  • R_curErrorBuf

Problematic:

  • SETLENGTH to make resizable vectors

We are not alone. Big actors have the same problem:

We may need to remove the point_metrics() function if we can't find a solution
@Jean-Romain Jean-Romain self-assigned this Jun 22, 2024
@Jean-Romain Jean-Romain added the CRAN A change that is required by the CRAN label Jun 22, 2024
@Jean-Romain
Copy link
Collaborator Author

Removed point_metrics() temporarily

@samuelgrubinger
Copy link

Hi JR,
Is there any plan to reinstate point_metrics()?
It would be very helpful. If it were available in lidR, I wouldn't need to do such 'fancy' things in lasR.
Unfortunately, I am working on a cloud computing system and can only install from conda-forge, so can't grab it from the devel version.

@Jean-Romain
Copy link
Collaborator Author

You can install it from r-universe. It's not my fault if CRAN changes its policies without providing a fallback. This also affects, for example, the data.table package, and they haven’t found a workaround yet. If world-class programmers can’t find a solution, I probably won’t either. Still, data.table remains on CRAN, maybe they can put more pressure on CRAN, I don’t know. If I release lidR with the feature, I’m pretty sure it will be kicked off CRAN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jean-Romain Jean-Romain

Labels
CRAN A change that is required by the CRAN
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Jean-Romain @samuelgrubinger
0