The main things seem to be related to (travis log is at
https://travis-ci.org/spatstat/s2/jobs/149578339):
1. Deprecated C++ headers <ext/hash_set> and <ext/hash_map>.
2. Compiled code that calls entry points which might terminate R or
write to stdout/stderr.
Is it hopeless to get on CRAN with warnings like these?
I don't set CRAN policy, but I would say yes. Problem 1 limits your
package to systems using compilers that support those antiquated
headers; R tries very hard to be portable across many systems. Problem
2 makes R potentially unstable.
Thanks for the quick reply. The non-portability issue you mention has
not shown up so far but I was actually fearing it would show up once I
(or more likely CRAN) try to compile on solaris -- is there a way to
test code on solaris without bothering the brave CRAN souls? Anyway, I
should probably start executing some sed commands and see if I can get
rid of the problem in a fairly reproducible way.
Regarding problem 2 even if I never use the part of the C++ code that
writes to stdout etc. I guess it is impossible for CRAN to know this, so
it makes sense for them to be safe rather than sorry?
/Ege
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
