On Tue, 2017-03-07 at 14:57 +0000, Gábor Csárdi wrote: > On Tue, Mar 7, 2017 at 2:51 PM, Dirk Eddelbuettel <e...@debian.org> > wrote: > [...] > > > But I just found that using string literals in .Call() works just > > > fine. Hopefully > > > this will still be allowed in the long run: > > > > > > .Call("c_non_existent_function_on_this_platform", ...) > > > > So you are adjusting the literals on the fly at compilation time? > > No, I just leave them there. They are not supposed to be called on a platform > where the C function does not exist, and even if they would be, that's just an > error, which is fine. > > I could dynamically include/exclude R code at install time, but that is not so > easy, either, I would probably need to deal with the docs as well, etc. > > So I'll just leave it there....
You can put platform-specific R code and documentation in a subdirectory named "unix" or "windows". But there is no provision for MacOS-specific R code as far as I know. Martyn > G. > > > Dirk > > > > -- > > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel