suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add a note about where protected methods fit into our world

Browse Source
This commit is contained in:
Robby Findler 2011-06-03 20:05:22 -07:00
parent a4e72128af
commit 5848c1f5a6
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
collects/scribblings/guide/class.scrbl
View File

@ -348,6 +348,13 @@ and makes the overriding implementation augmentable.
@section[#:tag "extnames"]{Controlling the Scope of External Names} @section[#:tag "extnames"]{Controlling the Scope of External Names}
@margin-note{
Java's access control mechanisms (like @index["protected method"]{protected})
play a role similar to @racket[define-member-name], but
unlike in Java, Racket's mechanism for controlling access
is based on lexical scope, not the inheritance hierarchy.
}
As noted in @secref["intnames"], class members have both As noted in @secref["intnames"], class members have both
internal and external names. A member definition binds an internal internal and external names. A member definition binds an internal
name locally, and this binding can be locally renamed. External name locally, and this binding can be locally renamed. External