[Rd] R_CallMethodDef: 'type' and 'style' fields?

Steve Jaffe sjaffe at riskspan.com
Fri Oct 9 18:25:35 CEST 2009

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.

Duncan Temple Lang wrote:
> At present, a style of R_ARG_IN does not avoid duplicating the object.
> That could easily be activated and that was the intent, coupled with
> parameters being declared const. It is highly desirable to have that
> explicitly checked by the compiler rather than just stated in the
> declarations.
> And the idea is that all this meta information can be determined
> programmatically
> by examining the C code (e.g. with the RGCCTranslationUnit package).

View this message in context: http://www.nabble.com/R_CallMethodDef%3A-%27type%27-and-%27style%27-fields--tp25803313p25824090.html
Sent from the R devel mailing list archive at Nabble.com.

More information about the R-devel mailing list