| Line 22... |
Line 22... |
| 22 |
resulting call to \code{\link{setMethod}}.}
|
22 |
resulting call to \code{\link{setMethod}}.}
|
| 23 |
\item{signature}{the method signature, as it would be given to \code{\link{setMethod}}}
|
23 |
\item{signature}{the method signature, as it would be given to \code{\link{setMethod}}}
|
| 24 |
\item{file}{a character string name for the output file, or a
|
24 |
\item{file}{a character string name for the output file, or a
|
| 25 |
writable connection. By default the generic function name and
|
25 |
writable connection. By default the generic function name and
|
| 26 |
the classes in the signature are concatenated, with separating
|
26 |
the classes in the signature are concatenated, with separating
|
| 27 |
underscore characters. The file name should normally end in \code{".R"}. }
|
27 |
underscore characters. The file name should normally end in \code{".R"}.
|
| 28 |
|
28 |
|
| 29 |
To write multiple method skeletons to one file, open the file
|
29 |
To write multiple method skeletons to one file, open the file
|
| 30 |
connection first and then pass it to \code{method.skeleton()} in
|
30 |
connection first and then pass it to \code{method.skeleton()} in
|
| 31 |
multiple calls.
|
31 |
multiple calls.}
|
| 32 |
\item{external}{flag to control whether the function definition for
|
32 |
\item{external}{flag to control whether the function definition for
|
| 33 |
the method should be a separate external object assigned in the
|
33 |
the method should be a separate external object assigned in the
|
| 34 |
source file, or included in line in the call to
|
34 |
source file, or included in line in the call to
|
| 35 |
\code{\link{setMethod}}.
|
35 |
\code{\link{setMethod}}.
|
| 36 |
If supplied as a character string, this will be used as the name
|
36 |
If supplied as a character string, this will be used as the name
|
The R Project SVN
R