Incremental compiler for source-code development system

• US 5,182,806 A
• Filed: 06/30/1989
• Issued: 01/26/1993
• Est. Priority Date: 06/30/1989
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: McKeeman, William M., Aki, Shota
• Primary Examiner(s): Shaw, Gareth D.
• Assistant Examiner(s): Chaki, Kakali
• Application Number:
  US07/375,397
• Time in Patent Office: 1,306 Days
• Field of Search: 371/19, 364/192, 364/DIG. 1, 364/DIG. 2, 364/, 395/700
• US Class Current: 717/145
• CPC Class Codes: G06F 8/48 Incremental compilation software reuse G06F8/36
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44557 Code layout in executable memory

Abstract

A computer-aided software development system includes programs to implement edit, compile, link and run sequences, all from memory, at very high speed. The compiler operates on an incremental basis, line-by-line, so if only one line is changed in an edit session, then only that line need be recompiled if no other code is affected. Scanning is done incrementally, and the resulting token list saved in memory to be used again where no changes are made. All of the linking tables are saved in memory so there is no need to generate link tables for increments of code where no changes in links are needed. The parser is able to skip lines or blocks of lines of source code which haven'"'"'t been changed; for this purpose, each line of source text in the editor has a change-tag to indicate whether this line has been changed, and from this change-tag information a clean-lines table is built having a clean-lines indication for each line of source code, indicating how many clean lines follow the present line. All of the source code text modules, the token lists, symbol tables, code tables and related data saved from one compile to another are maintained in virtual memory rather than in files so that speed of operation is enhanced. Also, the object code created is maintained in memory rather than in a file, and executed from this memory image, to reduce delays. A virtual memory management arrangement for the system assures that all of the needed data modules and code is present in real memory by page swapping, but with a minimum of page faults, again to enhance operating speed.

Claims

1. A method of performing an edit-compile-link-run cycle upon source text using a programming development system executing on a computer, comprising the steps of:

a) generating a module of application source text, said source text being resident in a file system and held in memory in a source text buffer, the module of source text including a plurality of lines;

compiling said module of application source text to create a module of executable application code in said memory,

linking said module of application code to create in said memory an executable form of an application program, and executing said executable form of the application program from said memory;

b) editing some of the lines of said module of source text in said memory;

c) incrementally recompiling only lines of said module of application source text which have been changed by said editing to revise said module of executable application code, reusing said application code in said module corresponding to lines which have not been changed and are not dependent upon lines which have been changed;

said step of recompiling including the step of determining which lines of said source code have been changed by said editing or are dependent upon lines which have been changed, and including the step of generating object code for said module of application code for said lines which have been changed or are dependent upon lines which have been changed.

2. A method according to claim 1 wherein said step of recompiling includes the step of creating for each line of source text in said module in said source-text buffer an associated change-tag indicating whether the line of source text has been changed by said step of editing, and wherein said step of determining is in response to said change-tag.

3. A method according to claim 1 wherein said step of recompiling includes the step of creating a cleanlines table having, for each line of said source text, a table entry having a locator for the text of said line and an indication of the number of unmodified lines following said line;

and wherein said step of determining which lines have been changed uses said cleanlines table.

4. A method according to claim 1 wherein said steps of generating, editing, compiling, and recompiling are performed upon a number of said modules.

5. A method according to claim 1 including the step of stopping either of the steps of compiling, or recompiling, upon the detecting of an error.

6. A method of operating a source code development system on a computer, wherein a module of source text is first created in a step of editing by using an editor, said module being created in a source-text buffer as a plurality of lines including lines to be sequentially executed,

compiling the source text from said buffer to produce a code table,

linking said code table to produce a code image of executable object code, and

executing said code image to determine if there are errors in said source text,

comprising the steps of:

a) re-editing said module of source text using an editor to change selected lines of said source text, said re-edited source text being stored in said source-text buffer as a plurality of lines;

b) incrementally recompiling lines of said module from said source-text buffer which have been changed by said re-editing to produce an updated version of said code table while reusing code from said code table for lines of said module which have not been changed or are not dependent upon lines which have been changed;

said step of recompiling including the step of determining which of said lines of source text in said module have been changed by said re-editing and or are dependent upon lines which have been changed, and including the step of generating object code for said code table for said lines which have been changed or are dependent upon lines which have been changed.

7. A method according to claim 6 wherein said step of recompiling includes for each line in said source-text buffer generating an associated change-tag indicating whether the line of source text has been changed by said step of re-editing, and said step of determining using said change-tags.

8. A method according to claim 7 including the step of generating a clean-lines table including for each line of said source text a table entry, each said table entry having a locator for said line locating said line in said source text buffer and having an indication of the number of clean lines following said line, said indication being derived from evaluating said change-tags.

9. A method according to claim 8 wherein said step of recompiling includes the step of checking said clean-lines table to see if the number of clean lines following a selected line is greater than the number of lines of an increment of text.

10. A method according to claim 6 wherein said step of recompiling is halted to return an error indication if an error is detected.

11. A method according to claim 6 wherein there are a plurality of said modules compiled and linked to create said code image, and each of said modules is subjected to said steps of re-editing and incrementally recompiling.

12. A system for use on a computer in developing source code, wherein a module of source code is created and edited in a source-text buffer as a plurality of lines including lines to be sequentially executed, the source code from said buffer is compiled to produce object code in a code table, said code table is linked to produce a code image of executable object code, and said code image is executed to determine if there are errors in said source code, said system comprising:

a) means for re-editing said module of source code and storing said source code in said source-text buffer as a plurality of lines, each line having an associated change-tag;

b) means for incrementally recompiling only lines of source code from said source-text buffer which have been changed by said re-editing to produce an updated code table reusing code from said code table corresponding to lines which have not been changed and are not dependent upon lines which have been changed;

said means for incrementally recompiling including means responsive to said change-tags for determining which lines of said source code of said source-text buffer have been changed, and means for generating object code for said code table for said lines which have been changed or are dependent upon lines which have been changed.

13. A system according to claim 12 wherein said means for recompiling includes means responsive to said change-tags of said lines of source code for generating a clean-lines table including for each line of said source code of said module a table entry having a locator for said line and an indication of the number of clean lines following said line.

14. A system according to claim 13 wherein said means for recompiling includes means for determining the number of lines in an increment of said source code, and includes means for checking said clean-lines table to see if the number of clean lines is greater than the number of lines of said increment of source code.

15. A system according to claim 12 wherein said means for recompiling includes means for halting execution to return an error indication immediately if an error is detected.

16. A system according to claim 12 wherein the are a plurality of said modules compiled and linked to create said code image, and each of said modules is operated upon by said means for re-editing, and by said means for incrementally recompiling.

17. A method executing on a computer for incrementally recompiling a module of source text which has been previously compiled from a source-text buffer and linked to create a code image of executable object code, said code image being executed to detect errors in said source text, said module containing a plurality of lines of source text, comprising the steps of:

a) editing selected lines of said module of source text, said edited source text being stored in said source-text buffer as a plurality of lines;

b) incrementally recompiling each line of said source text which has been changed by said step of editing and each line of said source text which is dependent upon a line which has been changed to update said code image for changed lines in said source text and lines dependent upon changed lines, wherein lines of said source text not changed in said step of editing and not dependent upon changed lines are not recompiled and executable object code in said code image is reused for said lines not changed and not dependent upon changed lines.

18. A method according to claim 17 wherein said step of recompiling includes the step of generating for each line in said source-text buffer an associated change-tag indicating whether the line of source text has been changed by said step of editing.

19. A method according to claim 17 wherein said step of recompiling includes the step of generating a clean-lines table including for each line of said source code a table entry having a locator for said line and an indication of the number of clean lines following said line;

and wherein said step of recompiling also includes the step of referencing said clean lines table in generating object code for said code image.

20. A method according to claim 19 wherein said step of recompiling includes the step of checking said clean-lines table to see if the number of clean lines is greater than the number of lines of an increment of said source text to determine if object code need be generated for said increment.

21. A method according to claim 19 wherein said step of recompiling includes the step of checking said clean-lines table to see if an increment of source text is in a line which has not been changed to determine if object code need be generated for said increment.

22. A method according to claim 17 wherein there are a plurality of said modules compiled and linked to create said code image, and each of said modules is subjected to said steps of editing and incrementally recompiling.