| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (14 out of 23)

memory leak: A continual increase of memory use over time in an application. The most common cause of memory leaks is the creation of transient objects that the application never deletes.

memory meter: A G2 feature for measuring total memory use over time to detect memory leaks.

menu entry: A rectangular cell in a pulldown or popup menu that can contain an entry label, an icon, and/or an accelerator label, which you create by using the G2 Menu System (GMS).

menu specification: A G2 Menu System (GMS) specification that you use to configure the layout and behavior of the top menu bar and its menu entries.

method: A procedural program that defines a common behavior for a class. You invoke methods explicitly for a particular instance of a class. In object-oriented terms, an object's methods are its functions. See also method hierarchy and procedure.

method hierarchy: A set of methods associated with classes that determines the inherited behaviors of each class in the hierarchy. A class can inherit the default method of its parent or override the default by providing specific behavior.

middleware: A software product that provides interfaces to many real-time systems, including Distributed Control Systems (DCSs). See also distributed object standard.

mission-critical application: An application that focuses on the goal or goals that have the most potential impact on your overall organization. G2 is an intelligent real-time system (IRTS) that is well-suited for developing and deploying mission-critical applications.

modular knowledge base (KB): An application that consists of multiple G2 modules. You design and implement modular KBs to facilitate the development, maintenance, reuse, and extensibility of your application.

modularize: To break up a complex application into some number of smaller building blocks, or modules.

module: A building block for organizing related information in a complex G2 application. You structure a module along functional or structural lines, according to the needs of the application. An example of a functional module is the G2 Foundation Resources (GFR) utility module, which provides a set of capabilities for managing multi-module applications. An example of a structural module is the GUIDE utility, which provides a variety of end user interface components, each in its own module. See also modular knowledge base, modularize, and module prefix.

module hierarchy: Specifies the hierarchical dependencies between modules and the order in which they load. G2 loads modules from the bottom up. See also dependent module and independent module.

module prefix: A unique, short prefix, usually three to six letters, that you use as a naming convention for a module and all items and attributes within that module. Module prefixes allow you to merge modular applications without experiencing naming conflicts.

multiple inheritance: A form of inheritance whereby classes inherit their definitions from more than one class. See also primary direct superior class and linearize.

multi-threaded processing: A type of processing whereby an existing process either starts a new process or starts a new subthread, with or without wait states. You typically refer to multi-threaded processing in the context of procedural processing; however, rule-based processing is inherently multi-threaded. Contrast with single-threaded processing.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (14 out of 23)