** Document Series **

TIP is the acronym for [Tcl Improvement Proposal], a process put into place by the [Tcl Core Team] (TCT) for submitting changes to Tcl or Tk that would result in C API or script level API interfaces.

The home base for TIPs is http://www.purl.org/tcl/tip/ or http://tip.tcl.tk/ (they end up at the same place after magical behind-the-scenes URL rewriting)

For people who do not feel that they have the technical expertise to see a TIP through the process, at least for Tcl and Tk there is the [SourceForge] Feature Request mechanism.

** List (TIP's that have wiki pages) **

*** [TIP #257: Object Orientation for Tcl%|%257: Object Orientation for Tcl%|%] ***

*** [TIP #305: ANSI Escape Sequence Support for Windows's Console Channel Driver%|%305: ANSI Escape Sequence Support for Windows's Console Channel Driver%|%] ***

*** [Tip 148%|%148: Correct [[list]]-Quoting of the '#' Character%|%] ***

*** [Tip 407|407:The String Representation of Tcl Lists: the Gory Details ***


** Utility Program **
Long ago, when "[Unix]" often as not meant "[Solaris]" (except that
it was called "SunOS" then) or something now regarded as even more
recondite, [serial port] work generally involved the command-line utilities
tip(1) and cu(1)
([http://tautology.org/software/man/1/tip], or
[http://www.daemon-systems.org/man/tip.1.html], 
for example).  Questions sometimes still arise about these from new
readers of '''[Exploring Expect]''', because that venerable volume
was written at a time when tip(1) constituted a natural example for 
its lessons.  tip(1) and cu(1) functions now might be done by ckermit [http://www.columbia.edu/kermit/ckermit.html], minicom [http://alioth.debian.org/projects/minicom/],
...

[[Was tip(1) specifically a BSD creation?]]

<<categories>> TIP | Community | Glossary | Networking | Device Control