- •Important Information
- •Warranty
- •Copyright
- •Trademarks
- •Organization of This Manual
- •Conventions Used in This Manual
- •Related Documentation
- •Customer Communication
- •Introduction
- •Classes of External Code
- •Supported Languages
- •Macintosh
- •Microsoft Windows 3.1
- •Microsoft Windows 95 and Windows NT
- •Solaris
- •Steps for Creating a CIN
- •1. Place the CIN on a Block Diagram
- •2. Add Input and Output Terminals to the CIN
- •Input-Output Terminals
- •Output-Only Terminals
- •3. Wire the Inputs and Outputs to the CIN
- •4. Create .c File
- •Special Macintosh Considerations
- •5. Compile the CIN Source Code
- •Macintosh
- •THINK C for 68K (Versions 5-7)
- •Symantec C++ 8.0 for Power Macintosh
- •Metrowerks CodeWarrior for 68K
- •Metrowerks CodeWarrior for Power Macintosh
- •Microsoft Windows 3.x
- •Watcom C Compiler
- •Microsoft Windows 95 and Windows NT
- •Microsoft SDK C/C++ Compiler
- •Visual C++ for Windows 95 or Windows NT
- •Solaris 1.x
- •Solaris 2.x
- •6. Load the CIN Object Code
- •LabVIEW Manager Routines
- •Online Reference
- •Pointers as Parameters
- •Debugging External Code
- •DbgPrintf
- •Debugging CINs Under Windows 95 and Windows NT
- •Debugging CINs Under Sun or Solaris
- •Debugging CINs Under HP-UX
- •Introduction
- •CIN .c File
- •How LabVIEW Passes Fixed Sized Data to CINs
- •Scalar Numerics
- •Scalar Booleans
- •Refnums
- •Clusters of Scalars
- •Return Value for CIN Routines
- •Examples with Scalars
- •1. Place the CIN on the Block Diagram
- •2. Add Two Input and Output Terminals to the CIN
- •3. Wire the Inputs and Outputs to the CIN
- •4. Create the CIN Source Code
- •5. Compile the CIN Source Code
- •Macintosh
- •THINK C for 68K and Symantec C++
- •Microsoft Windows 3.x
- •Watcom C Compiler
- •Microsoft Windows 95 and Windows NT
- •Microsoft SDK Compiler
- •Microsoft Visual C++ Compiler
- •Solaris 1.x, Solaris 2.x, and HP-UX
- •6. Load the CIN Object Code
- •Comparing Two Numbers, Producing a Boolean Scalar
- •How LabVIEW Passes Variably Sized Data to CINs
- •Alignment Considerations
- •Arrays and Strings
- •Paths (Path)
- •Clusters Containing Variably Sized Data
- •Resizing Arrays and Strings
- •SetCINArraySize
- •NumericArrayResize
- •Examples with Variably Sized Data
- •Concatenating Two Strings
- •Working with Clusters
- •CIN Routines
- •Data Spaces and Code Resources
- •CIN Routines: The Basic Case
- •Loading a VI
- •Unloading a VI
- •Loading a New Resource into the CIN
- •Compiling a VI
- •Running a VI
- •Saving a VI
- •Aborting a VI
- •Multiple References to the Same CIN
- •Reentrancy
- •Code Globals and CIN Data Space Globals
- •Examples
- •Using Code Globals
- •Using CIN Data Space Globals
- •Calling a Windows 3.1 Dynamic Link Library
- •Calling a 16-Bit DLL
- •1. Load the DLL
- •2. Get the address of the desired function
- •3. Describe the function
- •4. Call the function
- •Example: A CIN that Displays a Dialog Box
- •The Block Diagram
- •The CIN Code
- •Compiling the CIN
- •Optimization
- •Introduction
- •Creating Shared External Subroutines
- •External Subroutine
- •Macintosh
- •THINK C Compiler and CodeWarrior 68K Compiler
- •MPW Compiler
- •Solaris 1.x, Solaris 2.x, and HP-UX
- •Calling Code
- •Macintosh
- •THINK C Compiler
- •CodeWarrior 68K Compiler
- •MPW Compiler
- •Solaris 1.x, Solaris 2.x, and HP-UX
- •Simple Example
- •External Subroutine Example
- •Compiling the External Subroutine
- •Macintosh
- •THINK C Compiler and CodeWarrior 68K Compiler
- •MPW Compiler
- •Microsoft Windows 3.1
- •Watcom C Compiler
- •Microsoft Windows 95 and Windows NT
- •Solaris 1.x, Solaris 2.x, and HP-UX
- •Calling Code
- •Compiling the Calling Code
- •Macintosh
- •THINK C Compiler
- •CodeWarrior 68K Compiler
- •MPW Compiler
- •Microsoft Windows 3.1
- •Watcom C Compiler
- •Microsoft Windows 95 and Windows NT
- •Solaris 1.x, Solaris 2.x, and HP-UX
- •Introduction
- •Basic Data Types
- •Scalar Data Types
- •Booleans
- •Numerics
- •Complex Numbers
- •char Data Type
- •Dynamic Data Types
- •Arrays
- •Strings
- •C-Style Strings (CStr)
- •Pascal-Style Strings (PStr)
- •LabVIEW Strings (LStr)
- •Concatenated Pascal String (CPStr)
- •Paths (Path)
- •Memory-Related Types
- •Constants
- •Memory Manager
- •Memory Allocation
- •Static Memory Allocation
- •Dynamic Memory Allocation: Pointers and Handles
- •Memory Zones
- •Using Pointers and Handles
- •Simple Example
- •Reference to the Memory Manager
- •Memory Manager Data Structures
- •File Manager
- •Introduction
- •Identifying Files and Directories
- •Path Specifications
- •Conventional Path Specifications
- •Empty Path Specifications
- •LabVIEW Path Specification
- •File Descriptors
- •File Refnums
- •Support Manager
- •Allocating and Releasing Handles
- •Allocating and Releasing Pointers
- •Manipulating Properties of Handles
- •AZHLock
- •AZHPurge
- •AZHNoPurge
- •AZHUnlock
- •Memory Utilities
- •ClearMem
- •MoveBlock
- •SwapBlock
- •Handle and Pointer Verification
- •Memory Zone Utilities
- •File Manager Data Structures
- •File/Directory Information Record
- •File Type Record
- •Path Data Type
- •Permissions
- •Volume Information Record
- •File Manager Functions
- •Performing Basic File Operations
- •FCreate
- •FCreateAlways
- •FMClose
- •FMOpen
- •FMRead
- •FMWrite
- •Positioning the Current Position Mark
- •FMSeek
- •FMTell
- •Positioning the End-Of-File Mark
- •FGetEOF
- •FSetEOF
- •Flushing File Data to Disk
- •FFlush
- •FExists
- •FGetAccessRights
- •FGetInfo
- •FGetVolInfo
- •FSetAccessRights
- •FSetInfo
- •Getting Default Access Rights Information
- •FGetDefGroup
- •FListDir
- •FNewDir
- •Copying Files
- •FCopy
- •Moving and Deleting Files and Directories
- •FMove
- •FRemove
- •Locking a File Range
- •FLockOrUnlockRange
- •Matching Filenames with Patterns
- •FStrFitsPat
- •Creating Paths
- •FAddPath
- •FAppendName
- •FAppPath
- •FEmptyPath
- •FMakePath
- •FNotAPath
- •FRelPath
- •Disposing Paths
- •FDisposePath
- •Duplicating Paths
- •FPathCpy
- •FPathToPath
- •Extracting Information from a Path
- •FDepth
- •FDirName
- •FName
- •FNamePtr
- •FVolName
- •FArrToPath
- •FFlattenPath
- •FPathToArr
- •FPathToAZString
- •FPathToDSString
- •FStringToPath
- •FTextToPath
- •FUnFlattenPath
- •Comparing Paths
- •FIsAPath
- •FIsAPathOrNotAPath
- •FIsEmptyPath
- •FPathCmp
- •Determining a Path Type
- •FGetPathType
- •FIsAPathOfType
- •FSetPathType
- •Manipulating File Refnums
- •FDisposeRefNum
- •FIsARefNum
- •FNewRefNum
- •FRefNumToFD
- •FRefNumToPath
- •Byte Manipulation Operations
- •Mathematical Operations
- •For THINK C Users
- •RandomGen
- •String Manipulation
- •BlockCmp
- •CPStrCmp
- •CPStrIndex
- •CPStrInsert
- •CPStrRemove
- •CPStrReplace
- •CPStrSize
- •CToPStr
- •HexChar
- •IsAlpha
- •IsDigit
- •IsLower
- •IsUpper
- •LStrCmp
- •LToPStr
- •PPStrCaseCmp
- •PPStrCmp
- •PStrCaseCmp
- •PStrCat
- •PStrCmp
- •PStrCpy
- •PStrNCpy
- •PToCStr
- •PToLStr
- •StrCat
- •StrCmp
- •StrCpy
- •StrLen
- •StrNCaseCmp
- •StrNCmp
- •StrNCpy
- •ToLower
- •ToUpper
- •Utility Functions
- •BinSearch
- •QSort
- •Time Functions
- •ASCIITime
- •DateCString
- •DateToSecs
- •MilliSecs
- •SecsToDate
- •TimeCString
- •TimeInSecs
- •Microsoft Windows 3.1, Windows 95, and Windows NT
- •Macintosh
- •How do I debug my CIN?
- •Can LabVIEW be used to call a DLL in Windows?
- •Glossary
- •Index
|
|
Chapter 7 File Manager Functions |
|
returns |
A boolean, which can have the following values for this function. |
||
|
Values |
Description |
|
|
TRUE |
Path is well formed and type is identical to ofType. |
|
|
FALSE |
Otherwise. |
|
|
|
|
|
FSetPathType
syntax MgErr FSetPathType(path, type);
FSetPathType changes the type of the specified path (which must be a valid path) to the specified type (relative or absolute).
|
Parameter |
Type |
Description |
|
path |
Path |
Path whose type you want to change. |
|
type |
int32 |
New type that you want the path to have. type can |
|
|
|
have the following values: |
|
|
|
• fAbsPath: The path is an absolute path. |
|
|
|
• fRelPath: The path is a relative path. |
returns |
MgErr, which can contain the errors in the following list. |
||
|
Error |
Description |
|
|
mgArgErr |
Badly formed path or invalid type. |
|
|
|
|
|
Manipulating File Refnums
FDisposeRefNum
syntax |
MgErr |
FDisposeRefNum(refNum); |
FDisposeRefNum disposes of the specified file refnum.
|
Parameter |
Type |
Description |
|
refNum |
LVRefNum |
File refnum of which you want to dispose. |
returns |
MgErr, which can contain the errors in the following list. |
||
|
Error |
Description |
|
|
mgArgErr |
Invalid file refnum. |
|
|
|
|
|
National Instruments Corporation |
7-39 |
LabVIEW Code Interface Reference Manual |
Chapter 7 File Manager Functions
FIsARefNum
syntax Bool32 FIsARefNum(refNum);
FIsARefNum determines whether refNum is a valid file refnum.
|
Parameter |
Type |
Description |
|
|
refNum |
LVRefNum |
File refnum whose validity you want to determine. |
|
returns |
A boolean, which can have the following values for this function. |
|||
|
Value |
Description |
|
|
|
TRUE |
File refnum has been created and not yet disposed. |
||
|
FALSE |
Otherwise. |
|
|
|
|
|
|
|
FNewRefNum
syntax MgErr FNewRefNum(path, fd, refNumPtr);
FNewRefNum creates a new file refnum for an open file with the name and location specified by path and the file descriptor fd.
If the file refnum is created, the resulting file refnum is stored in the address referred to by refNumPtr. If an error occurs, NULL is stored in the address referred to by refNumPtr and the error is returned.
|
Parameter |
Type |
Description |
|
|
path |
Path |
The path of the open file for which you wish to |
|
|
|
|
create a file refnum. |
|
|
fd |
File |
The file descriptor of the open file for which you |
|
|
|
|
wish to create a file refnum. |
|
|
refNumPtr |
LVRefNum * Address at which FNewRefNum stores the new file |
||
|
|
|
refnum. |
|
|
|
|
See the Pointers as Parameters section of |
|
|
|
|
Chapter 1, CIN Overview, for more information |
|
|
|
|
about using this parameter. |
|
returns |
MgErr, which can contain the errors in the following list. |
|||
|
Error |
Description |
|
|
|
mgArgErr |
A bad argument was passed to the function. Verify path. |
||
|
mFullErr |
Insufficient memory. |
||
|
|
|
|
|
LabVIEW Code Interface Reference Manual |
7-40 |
National Instruments Corporation |
Chapter 7 File Manager Functions
FRefNumToFD
syntax |
MgErr |
FRefNumToFD(refNum, fdp); |
FRefNumToFD gets the file descriptor associated with the specified file refnum.
If no error occurs, the resulting file descriptor is stored in the address referred to by fdp. If an error occurs, NULL is stored in the address referred to by fdp and the error is returned.
|
Parameter |
Type |
Description |
|
|
refNum |
LVRefNum |
The file refnum whose associated file descriptor you |
|
|
|
|
wish to get. |
|
|
fdp |
File * |
Address at which FRefNumToFD stores the file |
|
|
|
|
descriptor associated with the specified file refnum. |
|
|
|
|
See the Pointers as Parameters section of |
|
|
|
|
Chapter 1, CIN Overview, for more information |
|
|
|
|
about using this parameter. |
|
returns |
MgErr, which can contain the errors in the following list. |
|||
|
Error |
Description |
|
|
|
mgArgErr |
Invalid file refnum. |
||
|
|
|
|
|
FRefNumToPath
syntax MgErr FRefNumToPath(refNum, path);
FRefNumToPath gets the path associated with the specified file refnum, and stores the resulting path in the existing path, path.
If no error occurs, path is set to the path associated with the specified file refnum. If an error occurs, path is set to the canonical invalid path.
Parameter |
Type |
Description |
refNum |
LVRefNum |
The file refnum whose associated path you wish to |
|
|
get. |
path |
Path |
Path where FRefNumToPath stores the path |
|
|
associated with the specified file refnum. This path |
|
|
must already have been created. |
returns |
MgErr, which can contain the errors in the following list. |
National Instruments Corporation |
7-41 |
LabVIEW Code Interface Reference Manual |
Chapter 7 File Manager Functions
Error |
Description |
mgArgErr |
A bad argument was passed to the function. Verify path. |
mFullErr |
Insufficient memory. |
|
|
LabVIEW Code Interface Reference Manual |
7-42 |
National Instruments Corporation |