National Instruments NI-488.2 - Manual (Page 40)

Chapter 4 Developing Your NI-488.2 Application
© National Instruments Corporation 4-3 NI-488.2 User Manual
For more information about direct entry access, refer to Directly Accessing
the gpib-32.dll Exports in the NI-488.2 Help.
Differences Between the GPIB32 API and NI4882 API
The NI-488.2 for Windows 2.6 release has introduced a new API as part of
the 64-bit application interface. Every effort has been made to have the new
NI4882 API closely match the existing GPIB32 API while incorporating
API design best practices. To use the new API, you must recompile
applications using the new header and object files. The following list
describes the major changes in the NI4882 API.
• Judicious application of the const keyword has been added where
appropriate.
• Wide variants of functions now use the wchar_t instead of unsigned
short type.
• Functions taking in parameters that describe a pointer length now use
size_t types.
• Status variables now use the unsigned long type.
• ThreadIbcntl has been removed. Macros redirect calls to
ThreadIbcnt .
• Global status functions have been added. These are Ibsta , Iberr ,
and Ibcnt . New code should use these functions instead of ibsta ,
iberr , or ibcnt / ibcntl .
• Long-term deprecated functions have been completely removed.
• Most functions with an ibconfig have been removed. Using
ibconfig is recommended for new code. Existing functions redirect
to using ibconfig using macros. These are the affected functions:
– ibpad
– ibsad
– ibtmo
– ibeot
– ibrsc
– ibsre
– ibeos
– ibdma
– ibist
– ibrsv
• Many macro definitions have been improved for programmatic safety.