Names of design patterns appear in small capitals: e.g., ADAPTER. Page numbers in bold indicate the definition of a term. Numbers in italics indicate a diagram for the term. Letters after a diagram's page number indicate the kind of diagram: a "c" denotes a class diagram, an "i" denotes an interaction diagram, and an "o" denotes an object diagram. For example, 88co means that a class and object diagram appears on page 88.

T

Target
participant of ADAPTER 141, 141c
TCP protocol 309
TCPConnection 305, 305c, 309
TCPSTATE 305, 305c, 310
template 21, see also parameterized types
used to implement COMMAND 239
used to implement FACTORY METHOD 113
used to implement Strategy 319, 323
Template Method 325
calling FACTORY METHODs 116
in catalog summary 9
naming conventions for 329
used to implement ITERATOR 270
template method 326
terminal symbol 246
shared using Flyweight 247
TerminalExpression
participant of Interpreter 245c, 246
TEX 42, 97, 316
TeXCompositor 42c, 315, 315c, 322
TextShape 139, 140c, 146, 147
TextView
use in ADAPTER 139, 140c, 146
use in DECORATOR 176c, 176o
ThingLab 125
THINK
use of COMMAND 242
use of OBSERVER 303
Token, see MEMENTO
Tool 117, 118c, 313, 313c
toolkit 26, 233, 362
see Andrew
see Booch Components
see Fresco
see InterViews
see IRIS Inventor
see Object Windows
see QOCA
see THINK
Transaction, see COMMAND
transaction 236
transparent enclosure 43, see also DECORATOR
traversal of aggregate objects, see also ITERATOR
across class hierarchies 336
assigning responsibility for in VISITOR 339
inorder, preorder, postorder 262
TreeAccessorDelegate 145, 145c
TreeDisplay 142, 144, 144c, 145c
two-way adapter, see adapter, two-way
type 13
compared with class 16
C++, definition in 17
Eiffel, definition in 17
Smalltalk, definition in 17
subtype 13
supertype 13
type-checking 332
to identify requests at run-time 228
see also dynamic_cast
TypeCheckingVISITOR 332c