Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Updated the abstract|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||dkf 2018-05-28 16:17:03|
|16:23||CFV for 500 by DKF check-in: db83e70e61 user: dkf tags: trunk|
|16:17||Updated the abstract check-in: b619dfd132 user: dkf tags: trunk|
|16:08||Clarify private method name interactions. check-in: 413ff82ed0 user: dkf tags: trunk|
Changes to tip/500.md.
7 7 Post-History: 8 8 Keywords: Tcl, object orientation, visibility 9 9 Tcl-Version: 8.7 10 10 ----- 11 11 12 12 # Abstract 13 13 14 -This TIP proposes a mechanism for (somewhat) private variables in TclOO. 14 +This TIP proposes a mechanism for private methods and variables in TclOO. 15 +Private methods are methods that can only be called from methods of the same 16 +class. Private variables have names so that they are unlikely to be used 17 +by subclasses by accident (but can still be used from **vwait**, Tk, etc.) 15 18 16 19 # Rationale 17 20 18 21 One of the principles of object oriented programming is that classes should be 19 22 isolated from each other. This particularly includes the isolation of a 20 23 superclass (which might be in one package) from its subclasses (in other 21 24 packages) other than for its published API. The TclOO object system in Tcl 8.6