| Line 64... |
Line 64... |
| 64 |
from which it originally comes; in particular, and frequently, the
|
64 |
from which it originally comes; in particular, and frequently, the
|
| 65 |
package where a non-generic version of the function originated.
|
65 |
package where a non-generic version of the function originated.
|
| 66 |
For example, generic functions for all the functions in package \code{base} will
|
66 |
For example, generic functions for all the functions in package \code{base} will
|
| 67 |
have \code{"base"} as the package name, although none of them is an
|
67 |
have \code{"base"} as the package name, although none of them is an
|
| 68 |
S4 generic on that package.
|
68 |
S4 generic on that package.
|
| - |
|
69 |
These include most of the base functions that are primitives, rather than
|
| - |
|
70 |
true functions; see the section on primitive functions in the
|
| - |
|
71 |
documentation for \code{\link{setGeneric}} for details.
|
| 69 |
|
72 |
|
| 70 |
Multiple packages can have methods for the same generic function; that
|
73 |
Multiple packages can have methods for the same generic function; that
|
| 71 |
is, for the same combination of generic function name and package
|
74 |
is, for the same combination of generic function name and package
|
| 72 |
name.
|
75 |
name.
|
| 73 |
Even though the methods are stored in separate tables in separate
|
76 |
Even though the methods are stored in separate tables in separate
|