Itcl
From Wikipedia, the free encyclopedia
Itcl | |
---|---|
Paradigm | multi-paradigm: object-oriented, functional, Imperative, event-driven programming |
Appeared in | 1993 |
Designed by | Michael McLennan |
Developer | Michael McLennan |
Latest release | itcl3.0 |
Typing discipline | dynamic typing, everything can be treated as a string |
Influenced by | Tcl, C++ |
incr Tcl (the name is a pun on "C++", and often abbreviated to "itcl") is a set of object-oriented extensions for the Tcl programming language. It is widely used among the Tcl community, and is generally regarded as industrial strength[citation needed]. Itcl implementations exist as both a package that may be dynamically loaded by a Tcl application, as well as an independent standalone language with its own interpreter.
Contents |
[edit] Overview
[edit] Features
[edit] Namespace Support
Itcl allows namespaces to be used for organizing commands and variables.
Example:
namespace symbol {
namespace counter {
variable num 0
proc next {{by 1}} {
global num
incr num $by
return $num
}
}
proc next {name} {
return "$name[counter::next]"
}
}
::symbol::counter::num
[edit] C/C++ Code Integration
Itcl has built-in support for the integration of C/C++ code into Itcl classes.
[edit] Licensing
Itcl follows the same copyright restrictions as Tcl/Tk. You can use, copy, modify and even redistribute this software without any written agreement or royalty, provided that you keep all copyright notices intact. You cannot claim ownership of the software; the authors and their institutions retain ownership, as described in the "license.terms" files included in the standard distribution. For more information please see incrtcl.sourceforge.net/itcl/copyright.html.
[edit] See also
[edit] External links
- Itcl/incr Tcl project page
- Tcl package site
- tclweb project (there is a mailing list maintained at this site)
[edit] References
[incr Tcl] from the Ground Up by Chad Smith, published in January 2000.
- This is a complete reference manual for [incr Tcl], covering language fundamentals, OO design issues, overloading, code reuse, multiple inheritance, abstract base classes, and performance issues. Despite its breadth, it follows a tutorial, rather than encyclopedic, approach. This book is out of print as of September 2004.