From csardi.gabor at gmail.com  Tue Mar  7 15:47:50 2017
From: csardi.gabor at gmail.com (=?UTF-8?B?R8OhYm9yIENzw6FyZGk=?=)
Date: Tue, 7 Mar 2017 14:47:50 +0000
Subject: [Rd] Platform dependent native routine registration
In-Reply-To: <22718.51054.27893.394368@max.eddelbuettel.com>
References: <CABtg=KkBqR3+FGPUwaHA4UF=V7fqkhCmvGiKTZ=x3UPP4YRbiQ@mail.gmail.com>
	<22718.51054.27893.394368@max.eddelbuettel.com>
Message-ID: <CABtg=K=21nKnxtEWDTqafXGxTo8Ke_ET8Kh=SDRsd67N_oUQxw@mail.gmail.com>

On Tue, Mar 7, 2017 at 2:45 PM, Dirk Eddelbuettel <edd at debian.org> wrote:
[...]
>
> Could you resort to preprocessor conditioning to only compile the code
> relevant for a particular platform while hiding away the inapplicable parts?

Yes, I do exactly that. The problem is that the R code still has

.Call(c_non_existent_function_on_this_platform, ...)

and R CMD check picks up on that.

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", ...)

Gabor



[Rd] Platform dependent native routine registration
=?UTF-8?B?R8OhYm9yIENzw6FyZGk=?=