You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: vignettes/compatibility.Rmd
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ library(S7)
26
26
S7 objects *are* S3 objects, because S7 is implemented on top of S3.
27
27
There are two main differences between an S7 object and an S3 object:
28
28
29
-
- As well as the `class` attribute possessed by S3 objects, S7 objects have an additional `S7_class` attribute that contains the object that defines the class.
29
+
- As well as the `class` attribute possessed by S3 objects, S7 objects have an additional `_S7_class` attribute that contains the object that defines the class.
30
30
31
31
- S7 objects have properties; S3 objects have attributes.
32
32
Properties are implemented on top of attributes, so you can access them directly with `attr` and friends.
@@ -219,7 +219,7 @@ There are a few important caveats:
219
219
After calling `S4_register()`, use `S4_contains()` when an S4 class should
220
220
extend an S7 class. It returns the virtual S4 class name for
221
221
`methods::setClass(contains = )`. This class exposes stored S7 properties as
222
-
formal S4 slots and carries the `S7_class` slot that S7 uses for dispatch and
222
+
formal S4 slots and carries the `_S7_class` slot that S7 uses for dispatch and
0 commit comments