IP Library Granted Patent US 8,302,084
Granted Patent B2
US 8,302,084 · App. 11/938,010 · Granted Oct 30, 2012

Using compiler commentary for configuring an integrated development environment

Assignee: Oracle America, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,302,084
App. No.
11/938,010
Granted
Oct 30, 2012
Kind
B2
Abstract

A technique is disclosed for correcting inconsistent language model parameters associated with a compiled computer readable project. One or more compiled units are analyzed to identify compiler commentary therein. Based on the debugging information, it is determined whether inconsistent language model parameters exist. If so, a user is allowed to apply a correction strategy to correct the one or more inconsistent parameters.

Claims (32)

1. A method for determining a structure of a computer program project, the project having one or more compilable units, the method comprising:

a) receiving program structure information from a user, the program structure information being described by program structure parameters that are used to provide navigational and syntax functionality, the program structures parameters including a symbol database and file database that keeps track of the interrelationships between project components;

b) analyzing at least one of the compilable units to identify compiler commentary contained therein;

c) discovering information about the program structure from the compiler commentary; and

d) reconciling the information obtained from steps a) and c).

2. The method of claim 1 wherein step d) is accomplish by a reconciliation strategy.

3. The method of claim 1 wherein the compiler commentary comprises debugger information.

4. The method of claim 1 wherein step d) comprises identifying one or more files unnecessary for compilation of the project.

5. The method of claim 3 further comprises indicating to the user files unnecessary for compilation.

6. The method of claim 5 wherein the one or more files unnecessary for compilation include at least one of the source compilation units.

7. The method of claim 5 wherein the source compilation units include at least one component selected from the group consisting of source files and header files.

8. The method of claim 2 wherein at least one inconsistent program structure parameter is defined by the project having missing project information, and the reconciliation strategy includes determining whether the project is missing project information.

9. The method of claim 8 wherein the reconciliation strategy includes programmatically restoring the missing project information.

10. The method of claim 8 wherein the missing project information includes the absence of at least one preprocessor directive of macro directives, conditional directives, and file inclusion directives.

11. The method of claim 1 wherein at least one inconsistent program structure parameter is defined by having at least one of the source compilation units with unidentified storage path locations.

12. The method of claim 11 wherein the correction strategy includes programmatically identifying storage locations for the source compilation units with unidentified storage path locations.

13. The method of claim 1 wherein the compiled units include at least one of object files, library files, and executable files.

14. An integrated development environment (IDE) providing code browsing functionality to a user, the IDE determining a program structure by the method comprising:

a) receiving program structure information from a user, the program structure information being described by program structure parameters that are used to provide navigational and syntax functionality, the program structure parameters including a symbol database and file database that keeps track of the interrelationships between project components;

b) analyzing at least one of the compilable units to identify compiler commentary contained therein;

c) discovering information about the program structure from the compiler commentary; and

d) reconciling the information obtained from steps a) and c) with a reconciliation strategy.

15. The IDE of claim 14 wherein at least one program structure parameter is defined by the project having one or more files unnecessary for compilation of the project.

16. The IDE of claim 14 wherein at least one inconsistent language program structure parameter is defined by the project having missing project information, and the reconciliation strategy includes determining whether the project is missing project information.

17. The IDE of claim 16 wherein the reconciliation strategy includes programmatically restoring the missing project information.

18. The IDE of claim 15 wherein at least one inconsistent program structure parameter is defined by having at least one of the source compilation units with unidentified storage locations.

19. The IDE of claim 18 wherein the reconciliation strategy includes programmatically identifying storage locations for the source compilation units with unidentified storage locations.

20. A computer readable medium comprising a set of instructions encoding a method for determining a program project structure, the project having one or more compilable units, the method comprising:

a) receiving program structure information from a user, the program structure information being described by program structure parameters that are used to provide navigational and syntax functionality, the program structure parameters including a symbol database and file database that keeps track of the interrelationships between project components;

b) analyzing at least one of the compilable units to identify compiler commentary contained therein;

c) discovering information about the program structure from the compiler commentary; and

d) reconciling the information obtained between steps a) and c).

Assignments (3)
MERGER AND CHANGE OF NAME Recorded Dec 16, 2015
From: ORACLE USA, INC.; SUN MICROSYSTEMS, INC.; ORACLE AMERICA, INC.
To: ORACLE AMERICA, INC.
Reel/Frame 037311/0182 →
CORRECTIVE ASSIGNMENT TO CORRECT THE STATE IN THE ADDRESS OF THE ASIGNEE PREVIOUSLY RECORDED ON REEL 020102 FRAME 0625. ASSIGNOR(S) HEREBY CONFIRMS THE STATE IN THE ADDRESS SHOULD BE CALIFORNIA (NOT COLORADO). Recorded Jan 15, 2008
From: SIMON, ALEXANDER; KRASNY, ANDREW
To: SUN MICROSYSTEMS, INC.
Reel/Frame 020365/0677 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 13, 2007
From: SIMON, ALEXANDER; KRASNY, ANDREW
To: SUN MICROSYSTEMS, INC.
Reel/Frame 020102/0625 →
Continuity (1)
Related Publication 20090125873A1 · May 14, 2009