Automatically updated cross reference system having increased flexibility

• US 6,064,814 A
• Filed: 11/13/1997
• Issued: 05/16/2000
• Est. Priority Date: 11/13/1997
• Status: Expired due to Term

• Current Assignee: Allen-Bradley Company LLC (Rockwell Automation, Inc.)
• Original Assignee: Allen-Bradley Company LLC (Rockwell Automation, Inc.)
• Inventors: Kalan, Michael D., Sepsi, Robert R., Capriles, Luis A.
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): Dam, Tuan Q.
• Application Number:
  US08/970,124
• Time in Patent Office: 915 Days
• Field of Search: 395/701, 395/703, 707/102-104, 707/1, 707/8, 707/203, 707/530, 707/511
• US Class Current: 717/116
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A method of maintaining cross reference information regarding a user program comprises the steps of determining that an aspect of a first referencee has been modified, notifying a first referencer that the aspect of the first referencee has been modified, and updating cross reference information. The notifying step is performed by the first referencee, and the updating step is performed by the first referencer. The cross reference information is stored in a database comprising an entry for each reference made by a referencer to a referencee. Each entry stores a unique identifiers which identify a respective referencer and referencee. The cross reference information is automatically updated through a notification procedure in which referencees are responsible for notifying referencers when an aspect of the referencee changes, and the referencers are thereafter responsible for updating the cross reference information. The present invention provides increased flexibility in terms of the types of cross reference information which is maintained and the types of actions which a user is allowed to take without losing cross reference information. For example, the cross reference system is able to manage references to a referencee before the referencee is created and after the referencee is deleted.

Claims

1. A method of maintaining cross reference information regarding a user program, said user program comprising a plurality of referencers which make references to a plurality of referencees, including a first referencer which makes a first reference to a first referencee, the method comprising the steps of:

determining that an aspect of said first referencee has been modified;

notifying said first referencer that said aspect of said first referencee has been modified, said notifying step being performed by said first referencee; and

updating said cross reference information, said updating step being performed by said first referencer.

2. A method according to claim 1, wherein said notifying step further comprises the following steps, performed by said referencee object:

accessing said cross reference information; and

determining, based on said cross reference information, that said first referencer references said first referencee.

3. A method according to claim 1, wherein said plurality of referencers includes a second referencer that makes a second reference to a non-existent referencee, and wherein the method further includes the step of maintaining cross reference information regarding said second reference by said second referencer to said non-existent referencee.

4. A method according to claim 3, wherein said storing step further comprises the steps of:

creating a temporary referencee;

maintaining said cross reference information regarding said second reference based on said temporary referencee;

creating a second referencee which corresponds to said non-existent referencee by converting said temporary referencee into said second referencee; and

maintaining cross reference information regarding said second reference based on said second referencee after said second reference is created.

5. A method according to claim 1, wherein said cross reference information is stored independently of user-given names of said plurality of referencers and said plurality of referencees.

6. A method according to claim 1, wherein said first referencee is a global variable, wherein said plurality of referencees further include a second referencee which is a local variable, and further comprising the steps of:

deleting said local variable;

updating references to said local variable so that said references to said local variable are instead made to said global variable.

7. A method according to claim 1, wherein there are multiple levels of referencers which are notified as a result of said modification to said first referencee, and wherein lower level referencers are updated before higher level referencers are updated.

8. A method according to claim 7,

wherein, for all referencees, said notifying step further comprises the following steps, which are performed recursively

(1) identifying referencer objects which reference a given referencee object, and determining whether a given referencer object is referenced by any upper level referencer objects which have not previously been identified,

(2) and, if so, then repeating said identifying step (1) with respect to the upper level referencers which have not been identified, and, if not, then repeating said identifying step (1) for another referencer until all referencers have been identified;

and

wherein, for all referencers, said updating step further comprises the following steps, which are performed recursively;

(1) determining whether a given referencer references any lower level referencers which reference said first referencee and which have not been updated,

(2) and, if so, then repeating said determining step (1) with respect to the lower level referencers which have not been updated, and, if not, then updating said given referencer and repeating said determining step (1) for another referencer until all referencers have been updated.

9. A method according to claim 1, wherein said cross reference information includes information regarding whether said first reference is destructive.

10. A method according to claim 1, wherein said first referencee comprises a plurality of subcomponents;

wherein said first referencer references one of said plurality of subcomponents of said referencee object; and

wherein said cross reference information includes information indicating which one of said plurality of subcomponents of said referencee is referenced by said referencer.

11. A method according to claim 1, wherein said method is implemented in an object-oriented programming environment.

12. A cross reference system for maintaining cross reference information regarding a user program in an object-oriented programming environment, the cross reference system comprising:

a referencee object;

a referencer object, said referencer object making a reference to said referencee object;

a database, said database maintaining cross reference information regarding said reference from said referencer object to said referencee object.

13. A cross reference system according to claim 12, wherein said database is automatically updated each time an aspect of said referencee object changes.

14. A cross reference system according to claim 12, wherein said referencee object is responsible for notifying said referencer object when an aspect of said referencee object changes, and wherein said referencer object is responsible for updating said database after being notified by said referencee object that said aspect of said referencee object has changed.

15. A cross reference system according to claim 12,

wherein said database stores a first unique identifier which identifies said referencee object;

and

wherein said database stores a second unique identifier which identifies said referencer object.

16. A cross reference system according to claim 12, wherein said database stores information regarding whether said reference from said referencer object to said referencee object is destructive.

17. A cross reference system according to claim 12,

wherein said references object comprises a plurality of subcomponents;

wherein said referencer object references one of said plurality of subcomponents of said referencee object; and

wherein said database stores information indicating which one of said plurality of subcomponents of said referencee object is referenced by said referencer object.

18. A cross reference system according to claim 12, further comprising a plurality of additional objects for which cross reference information is maintained, said plurality of additional objects being objects of different types including data objects, subroutine objects, and subroutine call objects.

19. A cross reference system according to claim 12, wherein said referencer object and said referencee object are objects of a control program for an industrial controller.

20. A cross reference system for maintaining information regarding references in a user program, the cross reference system comprising:

A. a plurality of referencees including first and second referencees,

1. said first referencee being assigned a first unique identifier, and

2. said second referencee being assigned a second unique identifier;

B. a plurality of referencers including first and second referencers,

1. said first referencer being assigned a third unique identifier, and said first referencer making a first reference to said first referencee,

2. said second referencer being assigned a fourth unique identifier, and said second referencer making a second reference to said second referencee; and

C. a database, said database including a plurality of entries including first and second entries,

1. said first entry corresponding to said first reference, said first entry including a first field which contains said first unique identifier and a second field which contains said third unique identifier, and

22. A cross reference system according to claim 20, wherein said first referencee is responsible for notifying said first referencer when an aspect of said first referencee changes, and wherein said first referencer is responsible for updating said database after being notified by said referencee that said aspect of said referencee has changed.

23. A cross reference system according to claim 20, wherein said first and second referencees and said first and second referencers are all objects of a control program for an industrial controller.

24. A cross reference system according to claim 20,

wherein said plurality of referencers includes a third referencer, said third referencer being assigned a fifth unique identifier, and said third referencer making a third reference to a non-existent referencee,

wherein said plurality of entries includes a third entry, said third entry corresponding to said third reference, said third entry including a first field which contains said fifth unique identifier and a second field which contains a sixth unique identifier, said sixth unique identifier being assigned to a temporary referencec which corresponds to said non-existent referencee.

21. said second entry corresponding to said second reference, said second entry including a first field which contains said second unique identifier and a second field which contains said fourth unique identifier.

25. A method of maintaining information regarding references in a user program, the method comprising the steps of:

A. making a reference to a non-existent referencee, said step (A) being performed a referencer;

B. creating a temporary referencee;

C. maintaining cross reference information regarding said reference based on said temporary referencee;

D. creating a new referencee which corresponds to said non-existent referencee by converting said temporary referencee into said new referencee; and

F. maintaining cross reference information regarding said reference based on said new referencee after said new referencee is created.

28. A cross reference system according to claim 25, wherein said first and second referencees and said first, second and third referencers are all objects of a control program for an industrial controller.

26. A cross reference system for assisting programming of a control program for an industrial control system, said cross reference system providing information regarding references in said control program to facilitate program editing, said cross reference system comprising:

A. a plurality of referencees including first and second referencees,

27. said first referencee being assigned a first unique identifier, and said first referencee comprising a subroutine, andsaid second referencee being assigned a second unique identifier, and said second referencee comprising a plurality of subcomponents;

B. a plurality of referencers including first, second and third referencers,

1. said first referencer being assigned a third unique identifier, said first referencer making a first reference to said first referencee, and said first referencer comprising a subroutine call to said subroutine,

2. said second referencer being assigned a fourth unique identifier, said second referencer making a second reference to said second referencee, and said second referencer referencing one of said plurality of subcomponents of said referencee,

3. said third referencer being assigned a fifth unique identifier, and said third referencer making a third reference to a non-existent referencee; and

C. a database, said database including a plurality of entries including first, second and third entries,

1. said first entry corresponding to said first reference, said first entry including a first field which contains said first unique identifier, said first entry including a second field which contains said third unique identifier, and said first entry including a third field which contains information regarding whether said first reference is destructive,

2. said second entry corresponding to said second reference, said second entry including a first field which contains said second unique identifier, said second entry including a second field which contains said fourth unique identifier, and said second entry including a third field which contains information regarding whether said third reference is destructive, and said second entry containing a fourth field containing information which indicates which one of said plurality of subcomponents of said referencee object is referenced by said referencer object, and

3. said third entry corresponding to said third reference, said third entry including a first field which contains said fifth unique identifier and a second field which contains a sixth unique identifier, said sixth unique identifier corresponding to a temporary referencee established to maintain cross reference information for said non-existent referencee; and

wherein said first referencee is responsible for notifying said first referencer when an aspect of said first referencee changes, and wherein said first referencer is responsible for updating said database after being notified by said first referencee that said aspect of said first referencee has changed;

wherein said second referencee is responsible for notifying said second referencer when an aspect of said second referencee changes, and wherein said second referencer is responsible for updating said database after being notified by said second referencee that said aspect of said second referencee has changed; and

wherein said database is automatically updated each time said aspect of said first referencee changes and each time said aspect of said second referencee changes.