search for: checkallpkgsapi

...n additional tools, which I would like to avoid for now. One dependency already present is that a C compiler has to be on the search path and cc -E has to run the C pre-processor.] Two additional experimental functions are available for analyzing package compliance: tools:::checkPkgAPI and tools:::checkAllPkgsAPI. These examine installed packages. [These may produce some false positives on macOS; they may or may not work on Windows at this point.] Using these tools initially showed around 200 non-API entry points used across packages on CRAN and BIOC. Ideally this number should be reduced to zero. This wi...

...h I would like to avoid for > now. One dependency already present is that a C compiler has to be on > the search path and cc -E has to run the C pre-processor.] > > Two additional experimental functions are available for analyzing > package compliance: tools:::checkPkgAPI and tools:::checkAllPkgsAPI. > These examine installed packages. > > [These may produce some false positives on macOS; they may or may not > work on Windows at this point.] > > Using these tools initially showed around 200 non-API entry points > used across packages on CRAN and BIOC. Ideally this number s...

...h I would like to avoid for > now. One dependency already present is that a C compiler has to be on > the search path and cc -E has to run the C pre-processor.] > > Two additional experimental functions are available for analyzing > package compliance: tools:::checkPkgAPI and tools:::checkAllPkgsAPI. > These examine installed packages. > > [These may produce some false positives on macOS; they may or may not > work on Windows at this point.] > > Using these tools initially showed around 200 non-API entry points > used across packages on CRAN and BIOC. Ideally this number s...

...h I would like to avoid for > now. One dependency already present is that a C compiler has to be on > the search path and cc -E has to run the C pre-processor.] > > Two additional experimental functions are available for analyzing > package compliance: tools:::checkPkgAPI and tools:::checkAllPkgsAPI. > These examine installed packages. > > [These may produce some false positives on macOS; they may or may not > work on Windows at this point.] > > Using these tools initially showed around 200 non-API entry points > used across packages on CRAN and BIOC. Ideally this number s...

...y already present is that a C compiler has to > be on > the search path and cc -E has to run the C pre-processor.] > > Two additional experimental functions are available for > analyzing > package compliance: tools:::checkPkgAPI and > tools:::checkAllPkgsAPI. > These examine installed packages. > > [These may produce some false positives on macOS; they may or > may not > work on Windows at this point.] > > Using these tools initially showed around 200 non-API entry > points > used acr...

...ler has to > > be on > > the search path and cc -E has to run the C pre-processor.] > > > > Two additional experimental functions are available for > > analyzing > > package compliance: tools:::checkPkgAPI and > > tools:::checkAllPkgsAPI. > > These examine installed packages. > > > > [These may produce some false positives on macOS; they may or > > may not > > work on Windows at this point.] > > > > Using these tools initially showed around 200 non-API entry &g...