Event handling in a high level programming language environment

• US 5,774,729 A
• Filed: 11/29/1993
• Issued: 06/30/1998
• Est. Priority Date: 12/19/1991
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Porter, Eric Lynn, Hochmuth, Gary John, Owings, Brian, Carney, William Peter, Wilson, Robert Aaron, England, Laurence Edward, Shannon, Alfred William
• Primary Examiner(s): TOPLU, LUCIEN
• Application Number:
  US08/159,063
• Time in Patent Office: 1,674 Days
• Field of Search: 364/DIG. 1, 364/DIG. 2, 395/700, 395/650, 395/707, 395/708
• US Class Current: 717/126
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A method and means for handling events in a computer system which occur during the execution of programs including routines prepared in a plurality of computer programming languages is described. The number and identity of each unique computer programming language used in the preparation of the program is determined using a language list contained in the application program. A unique event handling means (event handler) is initialized for each unique computer programming language used in the program. As the program executes selected events of interest to the event handlers are detected. The parameters associated with the selected event are determined. Optionally the detected events may be divided into two types: broadcast or targeted. Broadcast events are sent to all event handlers (except the debug event handler), whereas, the targeted events are sent to a single event handler. An event code and the relevant parameters are passed to the event handlers so that each event handler may perform whatever actions are appropriate for that event in the context of the programming language being supported. The event handlers generate an appropriate return code indicating the success, failure, or non-processing of the event and, for selected events, return request information. The invention provides for a separate specialized debug event handler.

Claims

1. A computer implemented method for managing event handling for processing events in a computer system, the events having associated parameters and occurring during the execution of a program, the program including routines prepared in a plurality of computer programming languages, the computer system having a common execution environment including an event handling unit and an Event Handler Interface Unit, comprising the steps of:

(a) determining, in a language list processor portion of the event handling unit, which of a plurality of computer programming languages are used in the program from high level language member identifiers for the program;

(b) initializing, in an event handler initializer portion of the event handling unit, based on the step of determining, a plurality of event handling means (event handlers) such that an event handler compatible with each computer programming language used in the program is initialized;

(c) detecting, in an event detector portion of the event handling unit, an occurrence of a selected event during execution of the program;

(d) determining, in the event handler interface unit, the computer programming language used in a currently executing routine and the associated parameters for the selected event;

(e) invoking, using the event handler interface unit, the initialized event handler compatible with the computer programming language used in the currently executing routine and passing an identifying event code and the associated parameters to said initialized event handler to cause the event to be handled, wherein the common execution environment is a single-run time environment; and

(f) repeating steps (c)-(e) each time a selected event occurs.

2. The method of claim 1, further comprising the steps of:

determining, in the event handler interface unit, whether the selected event is of a broadcast type which must be sent to all initialized event handlers; and

invoking in turn, using the event handler interface unit, for each broadcast type event, each initialized event handler not previously invoked by passing an identifying event code and the associated parameters to each initialized event handler for processing.

3. The method of claim 1, wherein the step of determining said plurality of computer programming languages used in said program further comprises determining said plurality of computer programming languages from high level language member identifiers contained in at least one program prologue area.

4. The method of claim 1, wherein said initializing step further comprises the steps of:

building an assigned name for each event handler using the high level language member identifiers; and

loading, from memory into the computer system each event handler using the assigned name.

5. The method of claim 1, further comprising the step of receiving, using the event handler interface unit, a return code from the event handler, the return code having a value indicative of success, non-processing or failure of processing of the event.

6. The method of claim 1, further comprising the step of receiving, using the event handler interface unit, return information from the event handler, said return information indicative of DSA Ownership, Entry Point and Compile Unit Identification, Statement Identification, or DSA Classification.

7. The method of claim 1, further comprising the step of initializing, using the event handling unit, a debug event handler.

8. The method of claim 7 wherein the system is capable of detecting error conditions, and the step of initializing the debug event handler is responsive to an initial command string, an error condition, or an express request from the program.

9. A computer implemented method for handling events for a computer programming language in a computer system having a processor, a common execution environment (CEE) having an event handling unit and an event handler interface unit, and an event handler, comprising the steps of:

(a) receiving, in the Event Handler Interface Unit, an Event Code and parameters corresponding to an event from the CEE;

(b) determining, in the event handler interface unit, whether the Event Code requires any information, including stack frame ownership information, entry point information, compile unit identification information, or a statement number which corresponds to an address from the event handler, responsive thereto finding the required information; and

(c) returning to the CEE any information found in step (b), wherein the CEE is a single-run time environment.

10. A computer system for handling events occurring during the execution of a program, the program including routines prepared in a plurality of computer programming languages, comprising:

means for determining which of a plurality of computer programming languages are used in the program from high level language member identifiers for the program;

means for initializing an event handling means (event handler) compatible with each computer programming language;

means for detecting an occurrence of a selected event during execution of the program;

means for determining the computer programming language used in a currently executing routine and parameters associated with the selected event; and

means for invoking an event handler compatible with the computer programming language used in the currently executing routine and passing an identifying event code and the associated parameters to the event handler to cause the event to be handled, wherein said identifying event code and said associated parameters are passed to the event handler through a common execution environment, and wherein said common execution environment is a single-run time environment.

11. The system of claim 10 further comprising:

means for determining whether the selected event is of a broadcast type which must be sent to all initialized event handlers; and

means for passing, for all broadcast type events, an identifying event code and the associated parameters to all initialized event handlers.

12. The system of claim 10 further comprising means for determining an event handler to which to pass the event code and the parameters using high level language member identifiers taken from a program prologue area.

13. The system of claim 10 wherein the means for initializing further comprises:

means for building a name for each event handler by using a preassigned member identifier; and

means for requesting dynamic loading of each event handler using the name.

14. The system of claim 10, further comprising means for receiving a return code from the event handler, the return code having a value indicative of success, non-processing or failure of processing of the event.

15. The system of claim 10 further comprising means for receiving return information from the event handler indicating DSA Ownership, Entry Point and Compile Unit Identification, Statement Identification, or DSA Classification.

16. The system of claim 10 further comprising means for initializing a debug event handler.

17. The system of claim 16 wherein the means for initializing the debug event handler is responsive to an initial command string, an error condition, or an express request from the program.