Parameterized packaging system for programming languages

• US 6,101,325 A
• Filed: 10/10/1996
• Issued: 08/08/2000
• Est. Priority Date: 10/10/1996
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Flaat, Christopher A.
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): NGUYEN BA, HOANG VU A
• Application Number:
  US08/728,891
• Time in Patent Office: 1,398 Days
• Field of Search: 395/701, 395/708, 395/702, 395/703, 395/704, 395/705, 395/706, 395/707, 395/709
• US Class Current: 717/136
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/423 Preprocessors
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A parameterized packaging system is provided for programming languages utilizing a preprocessor. A client of a package or facility may choose from among multiple interfaces for the package. Selection of a particular interface is made by passing interface parameters to the package in the package usage declarations. The proper package/interface file containing the definition of the requested interface is returned to the client in response to reading the interface parameters. Each interface of the available group of interfaces for a package is a fixed interface available for querying by a user of the package. Preprocessing is used in the creation of the interfaces as long as the preprocessor macros are only visible to the underlying package implementation and not the package interface. The developer is provided with the flexibility in design possible with the preprocessor as well as fixed and predictable package interfaces.

Claims

1. A method for selecting a package having a pre-defined set of interface elements in an application development system for a preprocessed computer programming language wherein said package is a programming module, said method comprising the steps of:

defining a group of package/interface files for said package, said package/interface files each having a different said pre-defined set of interface elements;

reading n interface parameters from a parameterized package usage declaration where n is an arbitrary number;

selecting a one of said package/interface files in response to reading said n interface parameters;

retrieving said one package/interface file; and

loading a set of package/interface symbols defining said pre-defined set of interface elements from said one package/interface file to a symbol table wherein said symbol table contains a global list of symbols known in said preprocessing computing environment.

2. The method of claim 1 wherein said step of defining said group of package/interface files for said package includes:

defining said n interface parameters, each of said n interface parameters having variations and a default value; and

building said package/interface files each having a unique said set of pre-defined interface elements.

3. The method of claim 2 wherein said step of defining said n interface parameters includes:

determining said group of said package/interface files necessary for said package wherein each one of said group of package/interface files represents a different version of said pre-defined set of interface elements to be made available to a user of said package; and

selecting said n interface parameters so that combinations of said n interface parameters uniquely identify ones of said group of said package/interface files.

4. The method of claim 2 wherein said step of building said package/interface files includes:

constructing an interface declaration for each said package/interface file of said group of package/interface files, said interface declaration containing a name of said package, a list of said n parameters unique to said packagerinterface file and definitions of the interface elements for said package/interface file.

5. The method of claim 4 wherein said step of building said package/interface files further includes:

parsing a one of said interface declarations to produce symbols; and

constructing, responsive to said preprocessing step, a one of said group of package/interface files.

6. The method of claim 5 wherein said parsing step includes:

preprocessing a macro contained within said interface declaration to produce symbols.

7. The method of claim 6 wherein said preprocessing step includes:

reading an interface package usage declaration within said interface declaration;

obtaining said macro from a second package responsive to said interface package usage declaration; and

preprocessing said macro to produce symbols.

8. The method of claim 5 wherein said constructing step includes:

parsing each line of said one interface declaration to produce symbols;

appending said symbols, responsive to said parsing step, to a symbol list containing said symbols for said one interface declaration.

9. The method of claim 8 wherein said constructing step further includes:

storing said symbol list associated with said one interface declaration as one of said package/interface files of said group of package/interface files.

10. The method of claim 1 wherein said step of selecting a one of said package/interface files includes:

building, responsive to said step of reading n interface parameters from a package usage declaration, a selected package/interface file having a unique said set of pre-defined interface elements.

11. The method of claim 10 wherein said step of defining said package/interface files includes:

determining said group of said package/interface files necessary for said package wherein each one of said group of package/interface files represents a different version of said pre-defined set of interface elements to be made available to a user of said package; and

selecting n interface parameters so that combinations of said n interface parameters uniquely identify ones of said group of said package/interface files.

12. The method of claim 11 wherein said step of defining said package/interface files includes:

constructing an interface declaration for each said package/interface file of said group of package/interface files, said interface declaration containing a name of said package, a list of said n parameters unique to said package/interface file and definitions of the interface elements for said package/interface file.

13. The method of claim 12 wherein said step of building said selected package/interface file includes:

selecting a one of said interface declarations responsive to said step of reading n interface parameters from a parameterized package usage declaration;

parsing said selected interface declaration; and

constructing, responsive to said parsing step, said selected package interface file.

14. The method of claim 13 wherein said parsing step includes:

preprocessing a macro contained within said interface declaration to produce symbols.

15. The method of claim 14 wherein said preprocessing step includes:

reading an interface package usage declaration within said interface declaration;

obtaining said macro from a second package responsive to said interface package usage declaration; and

preprocessing said macro to produce symbols.

16. The method of claim 13 wherein said constructing step includes:

parsing each line of said selected interface declaration to produce symbols;

appending said package symbols, responsive to said parsing step, to a package symbol list containing said symbols for said selected interface declaration.

17. The method of claim 16 wherein said constructing step further includes:

storing said package symbol list associated with said selected interface declaration as said selected package/interface file.

18. The method of claim 17 wherein said step of retrieving a one of said package/interface files includes:

retrieving said selected package/interface file.

19. The method of claim 18 wherein said loading step includes:

appending said package symbols from said selected package/interface file to said symbol table containing said global list of symbols, said global list of symbols containing said symbols known in said preprocessing computing environment.

20. The method of claim 19 wherein said loading step includes:

appending said package symbols from said selected package/interface file to a namespace associated with said symbol table wherein said symbol table and said namespace contain symbols known in said preprocessing computing environment.

21. The method of claim 20 wherein said loading step includes:

appending said package symbols from said selected package/interface file to said symbol table wherein said package symbols includes symbols and preprocessor macros.

22. A computer-readable medium having computer-executable instructions for selecting a package having a pre-defined set of interface elements in an application development system for a preprocessed computer programming language wherein said package is a programming module, said method steps comprising:

defining a group of package/interface files for said package, said package/interface files each having a different said pre-defined set of interface elements;

reading n interface parameters from a parameterized package usage declaration where n is an arbitrary number;

selecting a one of said packagerinterface files in response to reading said n interface parameters;

retrieving said one package/interface file; and

loading a set of package/interface symbols defining said pre-defined set of interface elements from said one package/interface file to a symbol table wherein said symbol table contains a global list of symbols known in said preprocessing computing environment.

23. The computer-readable medium of claim 22 wherein said step of defining said group of package/interface files for said package includes:

defining said n interface parameters, each of said n interface parameters having variations and a default value; and

building said package/interface files each having a unique said set of pre-defined interface elements.

24. The computer-readable medium of claim 23 wherein said step of defining said n interface parameters includes:

determining said group of said package/interface files necessary for said package wherein each one of said group of package/interface files represents a different version of said pre-defined set of interface elements to be made available to a user of said package; and

selecting said n interface parameters so that combinations of said n interface parameters uniquely identify ones of said group of said package/interface files.

25. The computer-readable medium of claim 23 wherein said step of building said package/interface files includes:

constructing an interface declaration for each said package/interface file of said group of package/interface files, said interface declaration containing a name of said package, a list of said n parameters unique to said package/interface file and definitions of the interface elements for said package/interface file.

26. The computer-readable medium of claim 25 wherein said step of building said package/interface files further includes:

parsing a one of said interface declarations to produce symbols; and

constructing, responsive to said preprocessing step, a one of said group of package/interface files.

27. The computer-readable medium of claim 26 wherein said parsing step includes:

preprocessing a macro contained within said interface declaration to produce symbols.

28. The computer-readable medium of claim 27 wherein said preprocessing step includes:

reading an interface package usage declaration within said interface declaration;

obtaining said macro from a second package responsive to said interface package usage declaration; and

preprocessing said macro to produce symbols.

29. The computer-readable medium of claim 26 wherein said constructing step includes:

parsing each line of said one interface declaration to produce symbols;

appending said symbols, responsive to said parsing step, to a symbol list containing said symbols for said one interface declaration.

30. The computer-readable medium of claim 29 wherein said constructing step further includes:

storing said symbol list associated with said one interface declaration as one of said package/interface files of said group of package/interface files.

31. The computer-readable medium of claim 22 wherein said step of selecting a one of said package/interface files includes:

building, responsive to said step of reading n interface parameters from a package usage declaration, a selected package/interface file having a unique said set of pre-defined interface elements.

32. The computer-readable medium of claim 31 wherein said step of defining said package/interface includes:

determining said group of said package/interface files necessary for said package wherein each one of said group of package/interface files represents a different version of said pre-defined set of interface elements to be made available to a user of said package; and

selecting n interface parameters so that combinations of said n interface parameters uniquely identify ones of said group of said package/interface files.

33. The computer-readable medium of claim 32 wherein said step of defining said package/interface files includes:

constructing an interface declaration for each said package/interface file of said group of package/interface files, said interface declaration containing a name of said package, a list of said n parameters unique to said packagerinterface file and definitions of the interface elements for said package/interface file.

34. The computer-readable medium of claim 33 wherein said step of building said selected package/interface file includes:

selecting a one of said interface declarations responsive to said step of reading n interface parameters from a parameterized package usage declaration;

parsing said selected interface declaration; and

constructing, responsive to said parsing step, said selected package interface file.

35. The computer-readable medium of claim 34 wherein said parsing step includes:

preprocessing a macro contained within said interface declaration to produce symbols.

36. The computer-readable medium of claim 35 wherein said preprocessing step includes:

reading an interface package usage declaration within said interface declaration;

obtaining said macro from a second package responsive to said interface package usage declaration; and

preprocessing said macro to produce symbols.

37. The computer-readable medium of claim 34 wherein said constructing step includes:

parsing each line of said selected interface declaration to produce symbols;

appending said package symbols, responsive to said parsing step, to a package symbol list containing said symbols for said selected interface declaration.

38. The computer-readable medium of claim 37 wherein said constructing step further includes:

storing said package symbol list associated with said selected interface declaration as said selected package/interface file.

39. The computer-readable medium of claim 38 wherein said step of retrieving a one of said package/interface files includes:

retrieving said selected package/interface file.

40. The computer-readable medium of claim 39 wherein said loading step includes:

appending said package symbols from said selected package/interface file to said symbol table containing said global list of symbols, said global list of symbols containing said symbols known in said preprocessing computing environment.

41. The computer-readable medium of claim 40 wherein said loading step includes:

appending said package symbols from said selected package/interface file to a namespace associated with said symbol table wherein said symbol table and said namespace contain symbols known in said preprocessing computing environment.

42. The computer-readable medium of claim 40 wherein said loading step includes:

appending said package symbols from said selected package/interface file to said symbol table wherein said package symbols includes symbols and preprocessor macros.