System and method for automatically generating an object-oriented class wrapper

• US 6,941,558 B2
• Filed: 10/31/2001
• Issued: 09/06/2005
• Est. Priority Date: 10/31/2001
• Status: Expired due to Fees

• Current Assignee: Agilent Technologies, Inc.
• Original Assignee: Agilent Technologies, Inc.
• Inventors: Hill, Russell Keith, Wolber, Susan Germaine
• Primary Examiner(s): BULLOCK JR, LEWIS ALEXANDER
• Application Number:
  US09/999,757
• Publication Number:
  US 20030084197A1
• Time in Patent Office: 1,406 Days
• Field of Search: 719/315, 719321-327
• US Class Current: 719/321
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

A system for automatically generating an object-oriented class wrapper to simplify writing of device enabling programs is disclosed. In a simplified embodiment, a storage device is utilized having plug and play drivers stored therein. Logic configured to encapsulate functions universal to the plug and play drivers and a vi session handle within a base class is also utilized. The system also comprises logic configured to assign a name for the object-oriented class wrapper; logic configured to enable use of functions defined by the plug and play drivers; logic configured to enable use of parameters associated with the functions defined by the plug and play drivers; and logic configured to limit acceptable values for the parameters in accordance with acceptable parameter values defined by the plug and play drivers.

Claims

1. A system for automatically generating an object-oriented class wrapper for plug and play drivers, comprising:

a memory; and

,

a processor programmed by software stored within said memory to perform the steps of;

generating an object-oriented class wrapper responsive to header and front panel files associated with a plug and play compliant device driver;

encapsulating functions universal to said plug and play drivers and a vi session handle within a base class responsive to an alphanumeric identifier of a target device associated with the device driver, wherein the alphanumeric identifier is checked for conflicts with base class system objects;

assigning a name for said object-oriented class wrapper responsive to the alphanumeric identifier, wherein assigning comprises appending a suffix when a conflict exists;

enabling use of functions defined by said plug and play drivers; and

enabling use of parameters associated with said functions defined by said plug and play drivers.

2. The system of claim 1, wherein said object-oriented class wrapper is created in response to a request from a programmer to communicate with a device connected to said system.

3. The system of claim 2, wherein said step of enabling use of said functions generates source code for a first generated function and a second generated function, wherein said first generated function provides error reporting via return of a value previously defined by said programmer, and wherein said second generated function provides error reporting via triggering Structured Exception Handling.

4. The system of claim 1, wherein said plug and play drivers are VXIplug&

play drivers.

5. The system of claim 1, wherein said object-oriented class wrapper is generated from said base class and a child class, said child class comprising said encapsulated functions in addition to functions defined by a single one of said plug and play drivers, and parameters associated with said single one of said plug and play drivers, wherein a single child class is developed for each said plug and play driver.

6. The system of claim 5, wherein each of said encapsulated functions, said functions defined by a single one of said plug and play drivers, and said parameters associated with said single one of said plug and play drivers comprises a unique name.

7. The system of claim 1, wherein said step of assigning a name for said object-oriented class wrapper is performed by utilizing a driver name provided by a .fp driver file and a .h driver file.

8. The system of claim 1, further comprising the step of providing a graphical interface for selection of said functions and said parameters, wherein said graphical interface is defined by said plug and play drivers.

9. The system of claim 8, wherein said graphical interface also provides help information associated with said functions and said parameters.

10. A system for automatically generating an object-oriented class wrapper for plug and play drivers, comprising:

a memory comprising;

logic configured to encapsulate functions universal to said plug and play drivers and a vi session handle within a base class;

logic configured to assign a name for said object-oriented class wrapper;

logic configured to enable use of functions defined by said plug and play drivers by examining and converting plug and play data types to a common language runtime data type; and

logic configured to enable use of parameters associated with said functions defined by said plug and play drivers.

11. The system of claim 10, wherein said object-oriented class wrapper is generated from said base class and a child class, said child class comprising said encapsulated functions in addition to functions defined by a single one of said plug and play drivers, and parameters associated with said single one of said plug and play drivers, wherein a single child class is developed for each said plug and play driver.

12. The system of claim 11, wherein each of said encapsulated functions, said functions defined by a single one of said plug and play drivers, and said parameters associated with said single one of said plug and play drivers comprises a unique name.

13. The system of claim 10, wherein said assigning a name for said object-oriented class wrapper is performed by utilizing a driver name provided by a .fp driver file and a .h driver file.

14. The system of claim 10, further comprising logic to provide a graphical interface for selection of said functions and said parameters, wherein said graphical interface is defined by said plug and play drivers.

15. A method of automatically generating an computer-implemented object-oriented class wrapper for plug and play drivers, comprising the steps of:

encapsulating functions universal to said plug and play drivers and a vi session handle within a base class;

assigning a name for said object-oriented class wrapper responsive to an alphanumeric identifier, wherein assigning comprises appending a suffix when a conflict exists;

enabling use of functions defined by said plug and play drivers by examining and converting plug and play data types to a common language runtime data type; and

enabling use of parameters associated with said functions defined by said plug and play drivers.

16. The method of claim 15, wherein said object-oriented class wrapper is generated from said base class and a child class, said child class comprising said encapsulated functions in addition to functions defined by a single one of said plug and play drivers, and parameters associated with said single one of said plug and play drivers, wherein a single child class is developed for each said plug and play driver.

17. The method of claim 16, wherein each of said encapsulated functions, said functions defined by a single one of said plug and play drivers, and said parameters associated with said single one of said plug and play drivers comprises a unique name.

18. The method of claim 15, wherein said step of enabling use of said functions generates source code for a first generated function and a second generated function, wherein said first generated function provides error reporting via return of a previously defined value, and wherein said second generated function provides error reporting via triggering Structured Exception Handling.

19. A system for automatically generating an object-oriented class wrapper, comprising:

means for encapsulating functions universal to plug and play drivers stored within said system and a vi session handle within a base class;

means for assigning a name for said object-oriented class wrapper;

means for enabling use of functions defined by said plug and play drivers by examining and converting plug and play data types to a common language runtime data type; and

means for enabling use of parameters associated with said functions defined by said plug and play drivers.

20. The system of claim 19, wherein said object-oriented class wrapper is generated from said base class and a child class, said child class comprising said encapsulated functions in addition to functions defined by a single one of said plug and play drivers, and parameters associated with said single one of said plug and play drivers, wherein a single child class is developed for each said plug and play driver.