System and methods for providing versioning of software components in a computer programming language

• US 20060026568A1
• Filed: 09/30/2005
• Published: 02/02/2006
• Est. Priority Date: 07/05/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hejlsberg, Anders, Sollich, Peter F., Wiltamuth, Scott, Abrams, Bradley M.
• Granted Patent: US 7,873,958 B2
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system and methods for versioning software components in connection with a computer programming language are provided. In exemplary aspects, the versioning system makes use of intelligent defaults, provides a vehicle for unambiguous specification of developer intent and implements conflict resolution rules in connection with the versioning of software components. In another aspect, the versioning system bounds names at run-time, but does not bound offsets at compile-time.

Claims

1. A method for providing versioning support for at least one software component of an object-oriented programming language, the method operating on a computer and comprising:

specifying programmer intent with regard to versioning of said at least one software component by assigning at least one keyword to said at least one software component.

2. A method according to claim 1, wherein said assigning said at least one keyword includes assigning at least one of virtual, new and override keywords.

3. A method according to claim 1, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component overrides another software component.

4. A method according to claim 1, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component is capable of being overridden by another software component.

5. A method according to claim 1, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component hides another software component.

6. A method according to claim 1, wherein said at least one software component is at least one member of the object-oriented programming language and the object-oriented programming language is from one of the sources of origin identified by C#, FORTRAN, PASCAL, VISUAL BASIC, C, C++, and JAVA.

7. A method according to claim 1, wherein said specifying of programmer intent includes assigning intelligent defaults to said at least one software component in the absence of assigning said at least one keyword to said at least one software component.

8. A computer readable storage medium having stored thereon a plurality of computer-executable modules, the computer executable modules comprising:

a versioning mechanism enabling a programmer to specify intent with regard to versioning of at least one software component by assigning at least one keyword to said at least one software component.

9. A computer readable medium according to claim 8, wherein said assigning said at least one keyword includes assigning at least one of virtual, new and override keywords.

10. A computer readable medium according to claim 8, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component overrides another software component.

11. A computer readable medium according to claim 8, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component is capable of being overridden by another software component.

12. A computer readable medium according to claim 8, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component hides another software component.

13. A computer readable medium according to claim 8, wherein said at least one software component is at least one member of the object-oriented programming language and the object-oriented programming language is from one of the sources of origin identified by C#, FORTRAN, PASCAL, VISUAL BASIC, C, C++, and JAVA.

14. A computer readable medium according to claim 8, wherein said specifying of programmer intent includes assigning intelligent defaults to said at least one software component in the absence of assigning said at least one keyword to said at least one software component.

15. An object-oriented programming language stored on a computer for producing computer executable modules, comprising:

a versioning mechanism enabling a programmer to specify intent with regard to versioning of at least one software component by assigning at least one keyword to said at least one software component.

16. An object-oriented programming language stored on a computer according to claim 15, wherein said assigning said at least one keyword includes assigning at least one of virtual, new and override keywords.

17. An object-oriented programming language stored on a computer according to claim 15, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component overrides another software component.

18. An object-oriented programming language stored on a computer according to claim 15, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component is capable of being overridden by another software component.

19. An object-oriented programming language stored on a computer according to claim 15, wherein said assigning said at least one keyword to said at least one software component specifies programmer intent with regard to whether said at least one software component hides another software component.

20. An object-oriented programming language stored on a computer according to claim 15, wherein said specifying of programmer intent includes assigning intelligent defaults to said at least one software component in the absence of assigning said at least one keyword to said at least one software component.