EP0547840A2
Expired / Lapsed
EP
⏱️ 0.0 years remaining
Event handling in a high level programming language environment
Assignee: International Business Machines Corp
•
Filing: 1992-12-10
•
Granted: —
•
Expires: 2012-12-10
Abstract
Abstract Events occurring in a computer system during the execution of programs 12 including routines 17, 18 prepared in a plurality of computer programming languages is as described are handled by a number of event handling means. 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) 13, 14 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 requested information. The invention provides for a separate specialized debug event handler 15.
Inventors
- 👤 William Peter Carney
- 👤 Laurence Edward England
- 👤 Gary John Hochmuth
- 👤 Brian Owings
- 👤 Eric Lynn Porter
- 👤 Alfred William Shannon
- 👤 Robert Aaron Wilson
Bibliographic Details
Application Number
—
Jurisdiction
EP
Data Source
google_patents
Last Synchronized
2026-11-07 11:05
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/542
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
102 words
A method for handling 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, comprising the steps of: determining the unique computer programming languages used in the preparation of the program; initializing a unique event handling means (event handler) for each unique computer programming language; detecting an occurrence of a selected event during the execution of the program; determining the associated parameters for the selected event; and passing an identifying event code and the associated parameters to at least one event handler.
Claim 2
Independent Claim
102 words
A method for handling 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, comprising the steps of: determining the unique computer programming languages used in the preparation of the program; initializing a unique event handling means (event handler) for each unique computer programming language; detecting an occurrence of a selected event during the execution of the program; determining the associated parameters for the selected event; and passing an identifying event code and the associated parameters to at least one event handler.
Claim 3
Dependent Claim
40 words
The method of claim 1 further comprising the steps of: determining whether the selected event is of the broadcast type; and passing, for all broadcast type events, an identifying event code and the associated parameters to all initialized event handlers.
Claim 4
Dependent Claim
54 words
The method of claim 1 wherein the program has at least one prologue area containing a high level language member identifier, further comprising the step of determining an event handler to which to pass the event code and the parameters by using the high level language member identifier taken from the program prologue area.
Claim 5
Dependent Claim
39 words
The method of claim 1 wherein the initializing step further comprises the steps of: building an assigned name for each event handler using a preassigned member identifier; and requesting dynamic loading of each event handler using the assigned name.
Claim 6
Dependent Claim
30 words
The method of claim 1 further comprising the step of receiving a return code from the event handler indicative of success, non-processing or failure of the processing of the event.
Claim 7
Dependent Claim
31 words
The method of claim 1 further comprising the step of receiving return information from the event handler indicating DSA Ownership, Entry Point and Compile Unit Identification, Statement Identification, or DSA Classification.
Claim 8
Dependent Claim
15 words
The method of claim 1 further comprising the step of initializing a debug event handler.
Claim 9
Dependent Claim
37 words
The method of claim 7 wherein the step of initializing the debug event handler is responsive to the contents of an initial command string, the raising of an error condition, or an express request from the program.
Claim 10
Independent Claim
118 words
A method for operating an event handler in a computer system having a common execution environment (CEE), comprising the steps of: (a) receiving an Event Code and parameters from the CEE; (b) determining whether the event requires any action by the Event Handler and responsive thereto returning a code indicative of 'no action taken' to the CEE; (c) determining whether the event requires information from the event handler and responsive thereto finding the required information; (d) processing any event not handled in steps (b) or (c); and (e) returning to the CEE a code indicative of the success, non-processing or failure of the actions performed in steps (c) or (d) together with any information found in step (c).
Claim 11
Independent Claim
118 words
A method for operating an event handler in a computer system having a common execution environment (CEE), comprising the steps of: (a) receiving an Event Code and parameters from the CEE; (b) determining whether the event requires any action by the Event Handler and responsive thereto returning a code indicative of 'no action taken' to the CEE; (c) determining whether the event requires information from the event handler and responsive thereto finding the required information; (d) processing any event not handled in steps (b) or (c); and (e) returning to the CEE a code indicative of the success, non-processing or failure of the actions performed in steps (c) or (d) together with any information found in step (c).
Claim 12
Dependent Claim
32 words
The method of claim 9 wherein step (c) further comprises finding information to be returned to the CEE indicating DSA Ownership, Entry Point and Compile Unit Identification, Statement Identification, or DSA Classification.
Claim 13
Dependent Claim
99 words
A computer system adapted for handling events occurring during the execution of a program including routines prepared in a plurality of computer programming languages, comprising: means for determining the unique computer programming languages used in the preparation of the program; means for initializing a unique event handling means (event handler) for each unique computer programming language; means for detecting an occurrence of a selected event during the execution of the program; means for determining the parameters associated with the selected event; and means for passing an identifying event code and the associated parameters to at least one event handler.
Claim 14
Dependent Claim
99 words
A computer system adapted for handling events occurring during the execution of a program including routines prepared in a plurality of computer programming languages, comprising: means for determining the unique computer programming languages used in the preparation of the program; means for initializing a unique event handling means (event handler) for each unique computer programming language; means for detecting an occurrence of a selected event during the execution of the program; means for determining the parameters associated with the selected event; and means for passing an identifying event code and the associated parameters to at least one event handler.
Claim 15
Dependent Claim
40 words
The system of claim 11 further comprising: means for determining whether the selected event is of the broadcast type; and means for passing, forall broadcast type events, an identifying event code and the associated parameters to all initialized event handlers.
Claim 16
Dependent Claim
37 words
The system of claim 11 further comprising means for determining an event handler to which to pass the event code and the parameters by using a high level language member identifier taken from a program prologue area.
Claim 17
Dependent Claim
40 words
The system of claim 11 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.
Claim 18
Dependent Claim
29 words
The system of claim 11 further comprising means for receiving a return code from the event handler indicative of success, non-processing or failure of the processing of the event.
Claim 19
Dependent Claim
30 words
The system of claim 11 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.
Claim 20
Dependent Claim
14 words
The system of claim 11 further comprising means for initializing a debug event handler.
Claim 21
Dependent Claim
37 words
The system of claim 17 wherein the means for initializing the debug event handler is responsive to the contents of an initial command string, the raising of an error condition, or an express request from the program.
References Cited (Backward Citations)
No citation records indexed.
USPTO Annuity & Maintenance Windows
Maintenance schedule is calculated for granted US utility patents.