Skip to content
Prev 34362 / 63424 Next

R_CallMethodDef: 'type' and 'style' fields?

Steve Jaffe wrote:
Good, glad that the manual is not erroneous. Thanks for confirming that.

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).
Yep. They are good things to declare when true.
Do be careful with DUP = FALSE, as the help page says.
Presumably there will be some parameters of your C function
that are not const so that you can modify them and return
results. (Unless of course the C routine is only of interest
for its side effects such as writing to a file.)

 D.