The Developer's Toolkit compiler supports both stream and low-level I/O. The primary difference between the two types of I/O is that low-level I/O leaves the responsibility of buffering and formatting up to you.

In general, you should not mix input or output from low-level I/O with that from stream I/O. The only way to communicate between stream I/O and low-level I/O is by using the fdopen or fileno functions.

The low-level I/O functions include: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ access ³ dup2 ³ fstat ³ _setmode ³
³ chmod ³ __eof ³ isatty ³ _sopen ³
³ _chsize ³ fdopen ³ lseek ³ stat ³
³ close ³ _filelength ³ open ³ _tell ³
³ creat ³ fileno ³ read ³ umask ³
³ dup ³ ³ ³ write ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

When you use the low-level I/O functions, you should be aware of the following:

• A handle is a value that identifies a file. It is created by the system and used by low-level I/O functions. For The Developer's Toolkit, the handle returned by low-level I/O functions like open (called the C_handle) is the same as that returned by DosOpen (called the API_handle). As a result, you can get a file handle using the low-level I/O functions, and then use it with OS/2 APIs.

  Portability Note Other compilers may map the file handle so that the C_handle and API_handle are different. If you will be compiling your programs with other compilers, do not write code that depends on the file handles being the same.

  You can pass handles between library environments without restriction. If you acquire a handle other than by using The Developer's Toolkit library functions open, creat, _sopen, or fileno, you must run _setmode for that handle before you use it with other The Developer's Toolkit library functions.

  
  The default open-sharing mode is SH_DENYWR. Use _sopen to obtain other sharing modes.
  
  Text mode deletes '\r' characters on input and changes '\n' to '\r\n' on output.
  
  In a multithread environment, you must ensure that two threads do not attempt to perform low-level I/O operations on the same file at the same time. You must make sure that one I/O process is completed before another begins.
  
  If the file mode is text, the low-level I/O functions treat the character 'x1a' in the following ways:

  • If it is detected in a nonseekable file, 'x1a' is treated as end-of-file. In a seekable file, it is treated as end-of-file only if it is the last character.
    
  • If a file is opened as text with either the O_APPEND or O_RDWR flags and 'x1a' is the last character of the file, the last character of the file is deleted.

  ---

  [Back] [Next]