Adding new compiler methods to an integrated development environment

• US 20040268301A1
• Filed: 06/16/2003
• Published: 12/30/2004
• Est. Priority Date: 06/16/2003
• Status: Abandoned Application

• Current Assignee: Mainsoft
• Original Assignee: Mainsoft
• Inventors: Kaston, Yaakov
• Application Number:
  US10/462,038
• Publication Number:
  US 20040268301A1
• Time in Patent Office: Days
• US Class Current: 717/108
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/41 Compilation

Abstract

Adding new compilers and methods to an integrated development environment (IDE), such as Microsoft'"'"'s Visual Studio .Net®, is disclosed. This enables a programmer to develop, build and execute applications written in programming languages supported by new compilers, or new methods thereof, using an IDE such as the Visual Studio .Net framework. The integration of new compilers in the Visual Studio .Net is accomplished by using a COM interface wrapping technique further disclosed by the present invention.

Claims

1. A method for adding at least a Java compiler to an integrated development environment (IDE), wherein the method enables a programmer to develop a software application written in any programming language supported by the IDE and to execute the software application on at least a Java runtime environment, wherein the Java compiler is capable of compiling Microsoft intermediate language (MSIL) bytecodes into Java bytecodes, the method comprising:

a) entering a deployment programming language and a source programming language of the software application;

b) replacing each original deployment function of the IDE with a new deployment function of the Java compiler; and

,

c) building the software application.

2. The method of claim 1, further comprising:

d) entering a reference to an external file;

e) converting said external file to an assembly file; and

,

f) replacing said reference to said external file with a reference to said assembly file.

3. The method of claim 2, further comprising:

g) referencing to at least a namespace of the Java runtime environment; and

,

h) setting properties of the Java compiler.

4. The method of claim 3, wherein said namespace is used to display public program components.

5. The method of claim 1, wherein said deployment function is used to do at least one of the following:

build;

compile;

execute;

run; and

debug the software application.

6. The method of claim 1, wherein the IDE is at least the Microsoft Visual Studio for .Net, which includes a COM interface having a plurality of functions.

7. The method of claim 6, wherein the source programming language is at least one of:

C++ with managed extensions;

C# (C-Sharp);

Visual Basic .Net;

Pascal;

Cobol;

Java;

Jscript; and

J# (J-Sharp).

8. The method of claim 2, wherein said assembly file can be executed on a .Net platform.

9. The method of claim 8, wherein said external file is at least one of:

a Java reference file;

an enterprise Java beans (EJB) object; and

a component object model (COM) object.

10. The method of claim 6, wherein replacing said original deployment function is performed by implementing the COM interface'"'"'s functions, wherein said COM interface includes said original deployment function of said Microsoft Visual Studio for .Net.

11. The method of claim 10, wherein the following steps comprise implementing said COM interface'"'"'s functions:

a) determining the location of said original deployment function in a virtual table;

b) terminating execution if said COM interface is wrapped by a wrapper object,

c) allocating a new wrapper object if said COM interface is not wrapped by a wrapper object;

d) saving an address of said new wrapper object in a global wrapper table (GWT);

e) saving an address of said COM interface in a reference list;

f) terminating execution if said original deployment function is already replaced by said new deployment function;

g) saving a pointer to said new deployment function in said GWT; and

,

h) executing said new deployment function.

12. The method of claim 11, wherein said virtual table is a data structure comprising at least:

pointers to said COM interfaces; and

pointers to said original deployment function implemented by said COM interfaces.

13. The method of claim 11, wherein said virtual table is associated with a single COM object.

14. The method of claim 11, wherein said GWT is a data structure comprising at least:

said wrapper object'"'"'s address; and

a pointer to said new deployment function.

15. The method of claim 11, wherein said reference list is a data structure comprising at least:

the address of each wrapped COM interface.

16. The method of claim 11, further comprising saving said virtual table in a global table.

17. The method of claim 11, further comprising generating an error message prior to said method termination.

18. The method of claim 11, wherein executing said new deployment function further comprises:

a) replacing said COM interface'"'"'s address with said wrapper object'"'"'s address in a stack; and

,

b) jumping to an address pointed by said new deployment function'"'"'s pointer.

19. The method of claim 16, wherein said new deployment function is capable of executing said original deployment function.

20. The method of claim 19, wherein the following steps comprise executing said original deployment function by said new deployment function:

a) retrieving said COM interface'"'"'s address from said reference list;

b) retrieving said original deployment function'"'"'s address from said global table; and

,

c) jumping to said address of said original deployment function.

21. The method of claim 1, wherein said MSIL is generated using at least a .Net compiler.

22. The method of claim 21, wherein said .Net compiler is capable of compiling at least one of the following programming languages:

C++ with managed extensions;

C#;

Visual Basic;

Pascal;

Cobol;

Java;

J#; and

Jscript.

23. The method of claim 1, wherein said generated Java bytecodes can operate in conjunction with any Java runtime environment.

24. The method of claim 23, wherein said Java runtime environment comprises at least Java to enterprise edition (J2EE) platform and Java to standard edition (J2SE) platform.

25. A computer executable code for adding at least a Java compiler to an integrated development environment (IDE), wherein the code enables a programmer to develop a software application written in any programming language supported by the IDE and to execute the software application on at least a Java runtime environment, wherein the Java compiler is capable of compiling Microsoft intermediate language (MSIL) bytecodes into Java bytecodes, the code comprising the steps of:

a) entering a deployment programming language and a source programming language of the software application;

b) replacing each original deployment function of the IDE with a new deployment function of the Java compiler; and

,

c) building the software application.

26. The computer executable code of claim 25, further comprising the steps of:

d) entering a reference to an external file;

e) converting said external file to an assembly file; and

,

f) replacing said reference to said external file with a reference to said assembly file.

27. The computer executable code of claim 26, further comprising the steps of:

g) referencing to at least a namespace of the Java runtime environment; and

,

h) setting the properties page of the Java complier.

28. The computer executable code of claim 27, wherein said namespace is used to display public program components.

29. The computer executable code of claim 25, wherein said deployment function is used to do at least one of the following:

build;

compile;

execute;

run; and

debug the software application.

30. The computer executable code of claim 25, wherein the IDE is at least the Microsoft Visual Studio for .Net, which includes a COM interface having a plurality of functions.

31. The computer executable code of claim 30, wherein said source programming language is at least one of:

C++ with managed extensions;

C# (C-Sharp);

Visual Basic .Net;

Pascal;

Cobol;

Java;

Jscript; and

J# (J-Sharp).

32. The computer executable code of claim 26, wherein said assembly file can be executed on a .Net platform.

33. The computer executable code of claim 32, wherein said external file is at least one of:

a Java reference file, an enterprise Java beans (EJB) object, a component object model (COM) object.

34. The computer executable code of claim 30, wherein replacing said original deployment function is performed by implementing the COM interface'"'"'s functions, wherein said COM interface implements said original deployment functions of said Microsoft Visual Studio for .Net.

35. The computer executable code of claim 34, wherein the following steps comprise implementing said COM interface'"'"'s function interface:

a) determining the location of said original deployment function in a virtual table;

b) terminating execution if said COM interface is already wrapped by a wrapper object;

c) allocating a new wrapper object if said COM interface is not already wrapped by a wrapper object;

d) saving an address of said new wrapper object in a global wrapper table (GWT);

e) saving an address of said COM interface in a reference list;

f) terminating execution if said original deployment function is already replaced by said new deployment function;

g) saving a pointer to said new deployment function in said GWT; and

,

h) executing said new deployment function.

36. The computer executable code of claim 35, wherein said virtual table is a data structure comprising at least:

pointers to said COM interfaces; and

pointers to said original deployment functions implemented by said COM interfaces.

37. The computer executable code of claim 35, wherein said virtual table is associated with a single COM object.

38. The computer executable code of claim 35, wherein said GWT is a data structure comprising at least:

said wrapper object'"'"'s address and a pointer to said new deployment function.

39. The computer executable code of claim 35, wherein said reference list is a data structure comprising at least:

the address of each wrapped COM interface.

40. The computer executable code of claim 35, further comprising the step of saving said virtual table in a global table.

41. The computer executable code of claim 35, further comprising the step of:

generating an error message prior to said execution termination.

42. The computer executable code of claim 35, wherein executing said new deployment function further comprises the steps of:

a) replacing said COM interface'"'"'s address with said wrapper object'"'"'s address in a stack; and

,

b) jumping to an address pointed by said new deployment function'"'"'s pointer.

43. The computer executable code of claim 40, wherein said new deployment function is capable of executing said original deployment function.

44. The computer executable code of claim 43, wherein the following steps comprise executing said original deployment function by said new deployment function:

a) retrieving said COM interface'"'"'s address from said reference list;

b) retrieving said original deployment function'"'"'s address from said global table; and

,

c) jumping to said address of said original deployment function.

45. The computer executable code of claim 25, wherein said MSIL is generated using at least a .Net compiler.

46. The computer executable code of claim 45, wherein said .Net compiler is capable of compiling at least one of the following programming languages:

C++ with managed extensions;

C#;

Visual Basic;

Pascal;

Cobol;

Java;

J#; and

Jscript.

47. The computer executable code of claim 25, wherein said generated Java bytecodes can operate in conjunction with any Java runtime environment.

48. The computer executable code of claim 47, wherein said Java runtime environment comprises at least Java to enterprise edition (J2EE) platform and Java to standard edition (J2SE) platform.

49. An integrated development environment (IDE) capable of creating a software application, the IDE comprising a method for implementing functions of a component object model (COM) interface by a third party application, wherein the method is operative to replace an original function of the COM interface with a new function of the third party application, the method comprises the steps of:

a) determining the location of the original function in a virtual table;

b) terminating execution if the COM interface is already wrapped by a wrapper object;

c) allocating a new wrapper object if the COM interface is not already wrapped by a wrapper object;

d) saving an address of said new wrapper object in a global wrapper table (GWT);

e) saving an address of said COM interface in a reference list;

f) terminating execution if said original function is already replaced by said new function;

g) saving a pointer to said new function in said GWT; and

,

h) executing said new function.

50. The method of claim 49, wherein said virtual table is a data structure comprising at least:

a pointer to the COM interface; and

a pointer to the original deployment function implemented by the COM interface.

51. The method of claim 49, wherein said virtual table is associated with a single COM object.

52. The method of claim 49, wherein said GWT is a data structure comprising at least:

said wrapper object'"'"'s address; and

a pointer to the new deployment function.

53. The method of claim 49, wherein said reference list is a data structure comprising at least:

the address of each wrapped COM interface.

54. The method of claim 49, further comprising the step of:

saving said virtual table in a global table.

55. The method of claim 49, further comprising the step of generating an error message prior to said method termination.

56. The method of claim 49, wherein executing said new function further comprises the steps of:

a) replacing said COM interface'"'"'s address with said wrapper object'"'"'s address in a stack; and

,

b) jumping to an address pointed by the new deployment function'"'"'s pointer.

57. The method of claim 54, wherein the new function is capable of executing the original function.

58. The method of claim 57, wherein the following steps comprise executing the original deployment function by the new deployment function:

a) retrieving said COM interface'"'"'s address from said reference list;

b) retrieving said original deployment function'"'"'s address from said global table;

and,

c) jumping to said address of the original function.

59. The method of claim 49, wherein the third party application is at least a Java compiler.

60. The method of claim 59, wherein the Java compiler is capable of compiling Microsoft intermediate language (MSIL) bytecodes into Java bytecodes.

61. The method of claim 60, wherein the MSIL is generated using at least a .Net compiler.

62. The method of claim 49, wherein the IDE is at least the Microsoft Visual Studio for .Net.

63. An integrated development environment (IDE) capable of creating a software application, the IDE further comprising a computer executable code for implementing functions of component object model (COM) interface by a third party application, wherein the code is operative to replace an original function of the COM interface with a new function of the third party application, the code comprises the steps of:

a) determining the location of the original function in a virtual table;

b) terminating execution if the COM interface is already wrapped by a wrapper object;

c) allocating a new wrapper object if the COM interface is not already wrapped by a wrapper object;

d) saving an address of a wrapper object in a global wrapper table (GWT);

e) saving an address of the COM interface in a reference list;

f) terminating execution if the original function is already replaced by the new function;

g) saving a pointer to the new function in the GWT; and

,

h) executing the new function.

64. The computer executable code of claim 63, wherein said virtual table is a data structure comprising at least:

a pointer to the COM interface; and

a pointer to the original deployment function implemented by the COM interface.

65. The computer executable code of claim 63, wherein said virtual table is associated with a single COM object.

66. The computer executable code of claim 63, wherein said GWT is a data structure comprising at least:

said wrapper object'"'"'s address; and

a pointer to the new deployment function.

67. The computer executable code of claim 63, wherein said reference list is a data structure comprising at least said address of each said wrapped COM interface.

68. The computer executable code of claim 63, further comprising the step of:

saving said virtual table in a global table.

69. The computer executable code of claim 63, further comprising the step of generating an error message prior to said method termination.

70. The computer executable code of claim 63, wherein executing said new function further comprises the steps of:

a) replacing said COM interface'"'"'s address with said wrapper object'"'"'s address in a stack; and

,

b) jumping to an address pointed by the new deployment function'"'"'s pointer.

71. The computer executable code of claim 63, wherein the new function is capable of executing the original function.

72. The computer executable code of claim 63, wherein the following steps comprise executing the original deployment function by the new deployment function:

a) retrieving the COM interface'"'"'s address from said reference list;

b) retrieving the original deployment function'"'"'s address from the global table; and

,

c) jumping to said address of the original function.

73. The computer executable code of claim 63, wherein the third party application is at least a Java compiler.

74. The computer executable code of claim 73, wherein said Java compiler is capable of compiling Microsoft intermediate language (MSIL) bytecodes into Java bytecodes.

75. The computer executable code of claim 74, wherein the MSIL is generated using at least a .Net compiler.

76. The computer executable code of claim 63, wherein the IDE is at least the Microsoft Visual Studio for .Net.