Undo/redo technique for token-oriented representation of program code

• US 7,386,834 B2
• Filed: 06/28/2002
• Issued: 06/10/2008
• Est. Priority Date: 06/28/2002
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Urquhart, Kenneth B., Van De Vanter, Michael L.
• Primary Examiner(s): Dam; Tuan
• Assistant Examiner(s): RUTTEN, JAMES D
• Application Number:
  US10/185,761
• Publication Number:
  US 20040006764A1
• Time in Patent Office: 2,174 Days
• Field of Search: 717110-113, 717/530
• US Class Current: 717/110
• CPC Class Codes: G06F 8/33 Intelligent editors

Abstract

An editor or software engineering tool may be configured to represent program code as a doubly-linked list of lexical tokens and to maintain, coincident with an operation that modifies contents of the list, an undo object that identifies opposing end nodes of a sublist of one or more lexical tokens corresponding to a substring that is either inserted into or removed from the list by the operation. In this way, lexical tokens corresponding to an inserted substring can be readily and efficiently excised to restore a pre-insertion tokenized list state. Similarly, lexical tokens corresponding to a removed substring can be readily and efficiently reinstated to restore a pre-deletion tokenized list state. Advantageously, undo support once employed to restore a prior tokenized list state is symmetrically available to support redo operations. In some embodiments in accordance with the present invention, undo-redo entries are maintained in an operation ordered set that is traversed to support one or more operations in either the undo or redo directions. In some realizations, such an ordered set of undo-redo entries is maintained by, or in conjunction with, an undo-redo manager.

Claims

1. A method of providing undo operation support in an edit buffer, the method comprising:

representing the edit buffer as a doubly-linked list of nodes for a tokenized program representation, each node corresponding to a respective lexical token in the tokenized program representation; and

maintaining, as a side-effect of operations that modify contents of the list, an ordered set of undo objects that identify at least respective opposing-end nodes of respective sublists of one or more lexical tokens in the tokenized program representation corresponding to respective substrings inserted into the list by respective insert-type operations, wherein at least one of the sublists comprises different opposing end nodes stored non-contiguously and each of the sublists is a doubly linked list.

2. The method of claim 1, further comprising:

maintaining the ordered set of undo objects to further identify at least respective opposing-end nodes of respective doubly-linked sublists of one or more lexical tokens corresponding to respective substrings removed from the list by respective remove-type operations.

3. The method of claim 2,

wherein the opposing-end nodes of a particular sublist removed from the list by execution of a particular one of the remove-type operations maintain an identification of respective predecessor and successor nodes of the list prior to the execution of the particular remove-type operation.

4. The method of claim 2, further comprising:

restoring, coincident with an undo directive, the doubly-linked list of lexical tokens to a state that existed prior to execution of a particular remove-type operation at least in part by reintroducing thereinto the sublist identified by a corresponding one of the undo objects; and

maintaining as a redo object, identification of at least the opposing end nodes of the reintroduced sublist.

5. The method of claim 1,

wherein, for a particular lexical token of the list replaced by a replace-type operation, the maintaining includes encoding in a corresponding one of the undo objects an identification of the replaced token.

6. The method of claim 1,

wherein, for a particular lexical token of the list split by an insert-type operation, the maintaining includes replicating in a sublist inserted into the list, substrings corresponding to the split token;

and

wherein the corresponding one of the undo objects further identifies a particular node corresponding to the split token.

7. The method of claim 1, further comprising:

restoring, coincident with an undo directive, the doubly-linked list of lexical tokens to a state that existed prior to execution of a particular insert-type operation at least in part by removing therefrom the sublist identified by a corresponding one of the undo objects; and

maintaining as a redo object, identification of at least the opposing end nodes of the removed sublist.

8. The method of claim 7,

wherein the corresponding one of the undo objects and the redo object are encoded as a same object.

9. The method of claim 1,

wherein at least one of the undo objects identifies a sublist that includes a single lexical token, and wherein opposing-end nodes of the sublist are a same node.

10. A software engineering tool encoded in one or more computer readable media, the software engineering tool comprising:

a representation of program code encoded in a computer readable medium as a doubly-linked list of nodes for a tokenized program representation, each node corresponding to a respective token in the tokenized program representation recognized in accordance with an operative set of lexical rules;

functional encodings of edit methods, including at least insert-type and remove-type methods, the edit methods executable to operate on the list of nodes; and

an undo-redo manager that maintains an ordered set of undo-redo objects in correspondence with operation of the edit methods, the undo-redo objects identifying opposing-end nodes of sublists of tokens inserted into the list and removed therefrom by operation of the insert-type and remove-type methods, respectively, wherein at least one of the sublists comprises different opposing end nodes stored non-contiguously and each of the sublists is a doubly-linked list.

11. The software engineering tool of claim 10, further comprising:

a functional encoding of an undo directive that reverses effects of a previously executed edit method on state of the list, while maintaining the identification of opposing-end nodes of a corresponding doubly-linked sublist of tokens for use in a subsequent redo directive.

12. The software engineering tool of claim 10,

a functional encoding of a redo directive that reinstates effects of a previously executed edit method on state of the list, while maintaining the identification of opposing-end nodes of a corresponding sublist of tokens for use in a subsequent undo directive.

13. A software engineering tool encoded in one or more tangible computer readable media as instructions executable to represent program code as a doubly-linked list of lexical tokens for a tokenized program representation and to maintain, coincident with an operation that modifies contents of the list, a first undo object that identifies at least opposing end nodes of a sublist of one or more lexical tokens in the tokenized program representation corresponding to a substring that is either introduced into or removed from the list by the operation, wherein the sublist comprises different opposing end nodes stored non-contiguously and is a doubly-linked list.

14. The software engineering tool of claim 13,

wherein the operation is an insert-type operation and the sublist of lexical tokens corresponds to a substring introduced by the insert-type operation.

15. The software engineering tool of claim 13,

wherein the operation is an remove-type operation and the sublist of lexical tokens corresponds to a substring removed by the remove-type operation.

16. The software engineering tool of claim 13,

wherein the instructions are further executable, coincident with an undo directive, to restore the doubly-linked list of lexical tokens to a prior state using the sublist identified by the first undo object, and to maintain as a redo object identification of at least the opposing end nodes of the sublist.

17. The software engineering tool of claim 16,

wherein the first undo object and the redo object are encoded as a same object.

18. The software engineering tool of claim 13,

wherein an operation-ordered store of undo objects, including the first undo object, is maintained for use by the software engineering tool.

19. The software engineering tool of claim 13, further comprising:

an operation-ordered store of undo-redo objects, including the first undo object.

20. The software engineering tool of claim 13,

wherein the one or more tangible computer readable media are selected from the set of a disk, tape or other magnetic, optical, or electronic storage medium.

21. One or more tangible computer readable media encoding a data structure that represents contents of an edit buffer as a sequence of lexical tokens, the encoded data structure comprising:

a doubly linked list of nodes for a tokenized program representation;

token representations, each corresponding to at least one respective node of the list, wherein at least some of the token representations have associated substring encodings; and

an edit-operation-ordered representation of undo objects that each identify at least opposing end nodes of respective sublists of one or more lexical tokens in the tokenized program representation that correspond to substrings that are either introduced into or removed from the list by edit operations, wherein at least one of the sublists comprises different opposing end nodes stored non-contiguously and each of the sublists is a doubly-linked list.

22. The encoded data structure of claim 21,

wherein the identification of opposing end nodes allows reversal of substring introductions and removals in response to respective undo directives with a computational burden that is independent of size of the edit buffer and independent of size of the substrings introduced and removed.

23. The encoded data structure of claim 21, embodied as a software object that defines at least one of the edit operations.

24. The encoded data structure of claim 21,

wherein the one or more tangible computer readable media are selected from the set of a disk, tape or other magnetic, optical, or electronic storage medium.

25. An apparatus comprising:

storage for a computer readable encoding of an edit buffer represented as a sequence of lexical tokens for a tokenized program representation; and

means for maintaining an edit-operation-ordered representation of undo objects that each identify at least opposing end nodes of respective sublists of one or more lexical tokens in the tokenized program representation that correspond to substrings that are either introduced into or removed from the list by edit operations, wherein at least one of the sublists comprises different opposing end nodes stored non-contiguously and each of the sublists is a doubly-linked list.

26. The apparatus of claim 25, further comprising:

means for reversing a particular execution of one of the edit operations using the opposing-end nodes identification of a corresponding one of the undo objects.

27. The apparatus of claim 26, further comprising:

means for maintaining the opposing-end nodes identification corresponding to the reversed edit operation for use in reinstatement of the reversed edit operation.