Run-time modules for dynamically adjusting computer operation

• US 6,708,332 B2
• Filed: 08/13/2001
• Issued: 03/16/2004
• Est. Priority Date: 01/08/1999
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Apple Computer Incorporated (Apple Inc.)
• Inventors: Fitzgerald-Smith, Ken, Kateley, James, Murphy, Colm J., Han, Byron
• Primary Examiner(s): CHAVIS, JOHN Q
• Application Number:
  US09/927,581
• Publication Number:
  US 20020078434A1
• Time in Patent Office: 946 Days
• Field of Search: 717/111, 717/168, 717/174, 709/331
• US Class Current: 717/168
• CPC Class Codes: G06F 8/656 while running

Abstract

Code module interfaces are provided which allow a user to adjust the functionality of a program at run-time. The code module interfaces (CMIs) can be selectively activated by a user at run-time. Then, the control software will call the CMIs at various instances, for example, at startup, after each state change in the control software, at idle time and when the control software has completed all of its tasks. Alternatively, when each CMI is loaded, it can specify at which state change(s) that CMI is to be called to increase speed of operation.

Claims

1. A computer having stored thereon a computer program including at least one code module interface (CMI) defined by a first set of software code and a state machine defined by a second set of software code having a plurality of states each state having at least one predetermined exit criterion, said program executable by the computer for causing the computer to perform the steps of:

registering said at least one CMI during an initialization state of said state machine;

determining, based on said step of registering, at least one state within said state machine upon exit of which said at least one CMI is to be executed;

executing said CMI when said computer exits said at least one determined state within said computer program; and

re-entering said computer program at a state determined by said CMI, when said CMI executing step has ended, wherein functionality of said state machine is adjusted without altering said second set of software codes.

2. The computer of claim 1 wherein said CMI determines said re-entry state independently of said sate machine.

3. The computer of claim 1 wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said CMI is to be called.

4. The computer of claim 1 wherein the program further comprises the steps of:

executing said CMI at another of said at least one determined states in said state machine program; and

providing a variable set of arguments associated with the execution of said CMI, wherein said step of executing said CMI at said at least one determined state and said step of executing said CMI at said another of said at least one determined states are performed using different sets of arguments.

5. The computer of claim 1 wherein the program further comprises the step of:

providing, by said CMI, a plurality of subsets of code within said first set of software code, each of which subsets are associated with a different state of said state machine.

6. The computer of claim 5 wherein the step of executing further comprises the step of:

running one of said subsets of said first set of software code that is associated with a state of said state machine indicated by said at least one step.

7. A computer having stored thereon a computer program including at least one code module interface (CMI) plug-in module executable by the computer for causing the computer to perform the steps of:

registering said at least one plug-in module;

determining, based on said step of registering, at least one step within said computer program wherein said at least one plug-in module is to be executed;

executing said plug-in module when said computer reaches said step within said computer program; and

allowing said plug-in module to determine a re-entry step within said computer program for re-entering said computer program when said plug-in module executing step has ended.

8. The computer of claim 7 wherein said plug-in module determines said re-entry step independently of said computer program.

9. The computer of claim 7 wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said plug-in module is to be called.

10. The computer of claim 7 wherein the computer program further comprises the steps of:

executing said plug-in module at another step in said computer program; and

providing a variable set of arguments associated with execution of said plug-in module, wherein said step of executing said plug-in module at said at least one step and said step of executing said plug-in module at said another step are performed using different sets of arguments.

11. The computer of claim 7 wherein the computer program further comprises the step of:

providing, by said plug-in module, a plurality of sets of code, each of which are associated with a different state of said computer program.

12. The computer of claim 11 where said step of executing further comprises the steps of:

running one of said sets of code that is associated with a state of said computer program indicated by said at least one step.

13. A system to allow a user to adjust the functionality of a computer program which operates as a state machine at run-time, the system comprising:

a computer; and

a computer program stored on the computer, the computer program having at least one code module interface (CMI) defined by a first set of software code and a state machine defined by a second set of software code having a plurality of states, each state having at least one predetermined exit criterion, said program executable by the computer for causing the computer to perform the steps of;

registering said at least one CMI during an initialization state of said state machine;

determining, based on said step of registering, at least one state within said state machine upon exit of which said at least one CMI is to be executed;

executing said CMI when said computer exits said at least one determined state within said computer program; and

re-entering said computer program at a state determined by said CMI, when said CMI executing step has ended, wherein functionality of said state machine is adjusted without altering said second set of software codes.

14. The system of claim 13 wherein said CMI determines said re-entry state independently of said state machine.

15. The system of claim 13 wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said CMI is to be called.

16. The system of claim 13 wherein the program further comprises the steps of:

executing said CMI at another of said at least one determined states in said state machine program; and

providing a variable set of arguments associated with the execution of said CMI, wherein said step of executing said CMI at said at least one determined state and said step of executing said CMI at said another of said at least one determined states are performed using different sets of arguments.

17. The system of claim 13 wherein the program further comprises the step of:

providing, by said CMI, a plurality of subsets of code within said first set of software code, each of which subsets are associated with a different state of said state machine.

18. The system of claim 17 wherein the step of executing further comprises the step of:

running one of said subsets of said first set of software code that is associated with a state of said state machine indicated by said at least on step.

19. A system to allow a user to adjust the functionality of a computer program which operates as a state machine at run-time, the system comprising:

a computer; and

a computer program having at least one code module interface (CMI) plug-in module executable by the computer for causing the computer to perform the steps of;

registering said at least one plug-in module;

determining, based on said step of registering, at least one step within said computer program wherein said at least one plug-in module is to be executed;

executing said plug-in module when said computer reaches said step within said computer program; and

allowing said plug-in module to determine a re-entry step within said computer program for re-entering said computer program when said plug-in module executing step has ended.

20. The system of claim 19 wherein said plug-in module determines said re-entry step independently of said computer program.

21. The system of claim 19 wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said plug-in module is to be called.

22. The system of claim 19 wherein the computer program further comprises the steps of:

executing said plug-in module at another step in said computer program; and

providing a variable set of arguments associated with execution of said plug-in module, wherein said step of executing said plug-in module at said at least one step and said step of executing said plug-in module at said another step are performed using different sets of arguments.

23. The system of claim 19 wherein the computer program further comprises the step of:

providing, by said plug-in module, a plurality of sets of code, each of which are associated with a different state of said computer program.

24. The system of claim 23 where said step of executing further comprises the steps of:

running one of said sets of code that is associated with a state of said computer program indicated by said at least one step.