Hmm, I should have read the .C documentation more carefully still. I can't
use DUP=FALSE when passing character vectors. In that case, since specifying
the style doesn't suppress copying I guess my only option is to use the more
complicated .Call API, which I naturally was hoping to avoid.
Dunca
ich case it would seem to be a good
idea for me to make the signature of my C function declare the non-output
arguments to be const (eg const int* rather than int*).
Thanks for your help.
Duncan Temple Lang wrote:
>
>
>
> Steve Jaffe wrote:
>> In Writing R Extensions it is
In Writing R Extensions it is said that R_CallMethodDef has two optional
fields, 'type' and 'style' (where 'style' is said to distinguish
in/out/inout arguments). But it doesn't give the possible values for
'style'. Looking at the header Rdynload.h (version 2.9.2) it appears that
R_CallMethodDef
According to Writing R Extensions, the R_CallMethodDef struct has two
optional fields for specifying the 'type' and 'style' (where 'style' is said
to distinguish in/out/inout). But it gives no details of the possible values
of 'style'. And looking in the header file Rdynload.h the definition of
R_
