Browse Prior Art Database

RUN-TIME INITIALIZATION VIA PROGRAM SYMBOL TABLE

IP.com Disclosure Number: IPCOM000026481D
Original Publication Date: 1992-Apr-30
Included in the Prior Art Database: 2004-Apr-05
Document File: 2 page(s) / 101K

Publishing Venue

Xerox Disclosure Journal

Abstract

In large software systems, utility routines are often grouped into modules and placed into libraries. When the executable code for a system is linked, those symbols that are undefined in the modules being specifically linked are identified and searched for in the library modules. When found in the library, the modules containing the undefined symbols are also linked to produce the resultant executable code, Generally, the linking process also produces a symbol table which maps symbol string names to locations in memory, and may also include an indication of the data type for the symbol.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

XEROX DISCLOSURE JOURNAL

RUN-TIME INITIALIZATION VIA Proposed Classification PROGRAM SYMBOL TABLE U.S. C1.364/130
Lee C. Moore Int. C1. G05b

In large software systems, utility routines are often grouped into modules and placed into libraries. When the executable code for a system is linked, those symbols that are undefined in the modules being specifically linked are identified and searched for in the library modules. When found in the library, the modules containing the undefined symbols are also linked to produce the resultant executable code, Generally, the linking process also produces a symbol table which maps symbol string names to locations in memory, and may also include an indication of the data type for the symbol.

Often, the utility routines found in the libraries need to be initialized, using an initialization routine, before being used. Moreover, if a program uses a large number of these utility routines, there is potential for many initialization routine calls. Traditionally, calling the initialization routines has been handled in one of two ways: (1) the client program explicitly calls each initialization routine, or (2) the library module includes a single routine which calls the initialization routine for every module in that library. Disadvantages exist for both of these methods. First, option (1) requires the programmers to be aware of all utility routines called by the program on which they are working, as well as, all utility routines which are subsequently called by other utility routines. On the other hand, option (2) has the potential for wasting memory space and processing time by...