C/C++ Compiler (cl.hlp) (Table of Contents; Topic list)
Important Notice
The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.
Library Support for Keywords
                                             Up Contents Index Back
─────C/C++ Compiler─────────────────────────────────────────────────────────
 
     When using the __near, __far, __huge, and __based keywords to
     modify addressing conventions for particular items, you can
     usually use one of the standard libraries with your program. The
     large-model libraries are also used with huge-model programs.
 
     If you use the __near, __far, __huge, or __based keywords, also
     specify the standard include files to ensure that all pointer
     arguments are coerced to the correct types for the memory model
     you have selected.
 
     When calling library routines, you cannot pass far code pointers
     to library routines in a tiny-, small-, or compact-model library.
     You cannot pass far data pointers to library routines in a tiny,
     small, or medium data model. Note that the _halloc and _hfree
     functions are exceptions to this rule. The printf and scanf
     families of functions allow you to specify that you are passing a
     far pointer in your format specifier.
 
     Model-independent functions for string and buffer handling are
     provided. Model-independent functions are named _f<funcname>,
     where funcname is the name of a standard string or buffer-
     manipulation function.
     See: String Manipulation
          Buffer Manipulation
                                    -♦-