.Dd October 23, 2005 .Os Darwin .Dt COMPAT 5 .Sh NAME .Nm compat .Nd manipulate compatibility settings .Sh SYNOPSIS .Ev COMMAND_MODE=legacy|unix2003 .Lp .Fd #define _POSIX_C_SOURCE .Fd #define _DARWIN_C_SOURCE .Fd #define _NONSTD_SOURCE .Fd defined(__LP64__) .Lp .In sys/cdefs.h .Fd defined(_DARWIN_FEATURE_UNIX_CONFORMANCE) .Sh DESCRIPTION Setting the environment variable .Ev COMMAND_MODE to the value legacy causes utility programs to behave as closely to Mac OS X 10.3's utility programs as possible. When in this mode all of 10.3's flags are accepted, and in some cases extra flags are accepted, but no flags that were used in 10.3 will have been removed or changed in meaning. Any behavioral changes in this mode are documented in the LEGACY sections of the individual utilities. .Pp Setting the environment variable .Ev COMMAND_MODE to the value unix2003 causes utility programs to obey the .St -susv3 standards even if doing so would alter the behavior of flags used in 10.3. .Pp The value of .Ev COMMAND_MODE is case insensitive and if it is unset or set to something other than legacy or unix2003 it behaves as if it were set to unix2003. .Sh 32-BIT COMPILATION Defining .Dv _NONSTD_SOURCE causes library and kernel calls to behave as closely to Mac OS X 10.3's library and kernel calls as possible. Any behavioral changes in this mode are documented in the LEGACY sections of the individual function calls. .Pp Defining .Dv _POSIX_C_SOURCE or .Dv _DARWIN_C_SOURCE causes library and kernel calls to conform to the SUSv3 standards even if doing so would alter the behavior of functions used in 10.3. Defining .Dv _POSIX_C_SOURCE also removes functions, types, and other interfaces that are not part of SUSv3 from the normal C namespace, unless .Dv _DARWIN_C_SOURCE is also defined (i.e., .Dv _DARWIN_C_SOURCE is .Dv _POSIX_C_SOURCE with non-POSIX extensions). In any of these cases, the .Dv _DARWIN_FEATURE_UNIX_CONFORMANCE feature macro will be defined to the SUS conformance level (it is undefined otherwise). .Pp Starting in Mac OS X 10.5, if none of the macros .Dv _NONSTD_SOURCE , .Dv _POSIX_C_SOURCE or .Dv _DARWIN_C_SOURCE are defined, and the environment variable .Ev MACOSX_DEPLOYMENT_TARGET is either undefined or set to 10.5 or greater (or equivalently, the .Xr gcc 1 option .Fl mmacosx-version-min is either not specified or set to 10.5 or greater), then UNIX conformance will be on by default, and non-POSIX extensions will also be available (this is the equivalent of defining .Dv _DARWIN_C_SOURCE ) . For version values less that 10.5, UNIX conformance will be off (the equivalent of defining .Dv _NONSTD_SOURCE ) . .Sh 64-BIT COMPILATION When compiling for 64-bit architectures, the .Dv __LP64__ macro will be defined to 1, and UNIX conformance is always on (the .Dv _DARWIN_FEATURE_UNIX_CONFORMANCE macro will also be defined to the SUS conformance level). Defining .Dv _NONSTD_SOURCE will cause a compilation error. .Sh STANDARDS With COMMAND_MODE set to unix2003 utility functions conform to .St -susv3 . .Pp With .Dv _POSIX_C_SOURCE , .Dv _DARWIN_C_SOURCE , or .Dv __LP64__ , system and library calls conform to .St -susv3 . .Sh BUGS Different parts of a program can be compiled with different compatibility settings. The resultant program will normally work as expected, for example a regex created by the SUSv3 .Fn regcomp 3 can be passed to the legacy .Fn regfree 3 with no unexpected results. Some cases are less clear cut, for example what does the programmer intend when they use the SUSv3 .Fn regcomp 3 to compile a regex, but the legacy .Fn regexec 3 to execute it? Any interpretation will surprise someone.