| Line 40... |
Line 40... |
| 40 |
internal \R objects, passing the arguments to the code as a sequence
|
40 |
internal \R objects, passing the arguments to the code as a sequence
|
| 41 |
of \R objects. They assume C calling conventions, so can usually
|
41 |
of \R objects. They assume C calling conventions, so can usually
|
| 42 |
also be used of C++ code.
|
42 |
also be used of C++ code.
|
| 43 |
|
43 |
|
| 44 |
For details about how to write code to use with these functions see
|
44 |
For details about how to write code to use with these functions see
|
| 45 |
the chapter on \dQuote{System and foreign language interfaces} in
|
45 |
the chapter on \sQuote{System and foreign language interfaces} in
|
| 46 |
the \dQuote{Writing \R Extensions} manual. They differ in the way the
|
46 |
the \sQuote{Writing \R Extensions} manual. They differ in the way the
|
| 47 |
arguments are passed to the C code: \code{.External} allows for a
|
47 |
arguments are passed to the C code: \code{.External} allows for a
|
| 48 |
variable number of arguments.
|
48 |
variable number of arguments.
|
| 49 |
|
49 |
|
| 50 |
These functions are \link{primitive}, and \code{.NAME} is always
|
50 |
These functions are \link{primitive}, and \code{.NAME} is always
|
| 51 |
matched to the first argument supplied (which should not be named).
|
51 |
matched to the first argument supplied (which should not be named).
|