Lines Matching refs:code
15 directives at the top of your source code files. These directives
16 @emph{must} come before any @code{#include} of a system header file. It
27 some non-GNU programs define functions named @code{getline} that have
28 nothing to do with this library's @code{getline}. They would not be
42 The state of @code{_POSIX_SOURCE} is irrelevant if you define the
43 macro @code{_POSIX_C_SOURCE} to a positive integer.
52 If you define this macro to a value greater than or equal to @code{1},
56 If you define this macro to a value greater than or equal to @code{2},
60 If you define this macro to a value greater than or equal to @code{199309L},
65 @code{199506L}, then the functionality from the 1995 edition of the
69 @code{200112L}, then the functionality from the 2001 edition of the
73 @code{200809L}, then the functionality from the 2008 edition of the
76 Greater values for @code{_POSIX_C_SOURCE} will enable future extensions.
80 if you define @code{_POSIX_C_SOURCE} to a value greater than
81 or equal to @code{199506L}, then the functionality from the 1996
84 POSIX.1-2004 will always be included with a value of @code{200112L}.
92 POSIX.2 functionality and in fact @code{_POSIX_SOURCE} and
93 @code{_POSIX_C_SOURCE} are automatically defined.
98 If the macro @code{_XOPEN_SOURCE_EXTENDED} is also defined, even more
102 If the macro @code{_XOPEN_SOURCE} has the value @math{500} this includes
114 the functions @code{fseeko} and @code{ftello} are available. Without
116 (@code{fseek}, @code{ftell}) and the low-level POSIX interface
117 (@code{lseek}) would lead to problems.
133 contain @code{64} to indicate the intention, e.g., @code{off_t}
134 vs. @code{off64_t} and @code{fseeko} vs. @code{fseeko64}.
138 offsets are not generally used (see @code{_FILE_OFFSET_BITS}).
144 replacing the other. Whereas @code{_LARGEFILE64_SOURCE} makes the @w{64
146 @code{_FILE_OFFSET_BITS} allows the @w{64 bit} interface to
149 If @code{_FILE_OFFSET_BITS} is defined to the
150 value @code{32}, the @w{32 bit} interface is used and
151 types like @code{off_t} have a size of @w{32 bits} on @w{32 bit}
154 If the macro is defined to the value @code{64}, the large file interface
156 under different names (as they are with @code{_LARGEFILE64_SOURCE}).
158 call to @code{fseeko} now indeed calls @code{fseeko64}.
160 If the macro is not defined it currently defaults to @code{32}, but
162 @code{time_t} for Y2038 safety, and applications should not rely on
167 since the @code{*64} functions are identical to the normal functions.
174 Define this macro to control the bit size of @code{time_t}, and therefore
175 the bit size of all @code{time_t}-derived types and the prototypes of all
181 If @code{_TIME_BITS} is undefined, the bit size of @code{time_t} is
188 If @code{_TIME_BITS} is defined to be 64, @code{time_t} is defined
189 to be a 64-bit integer. On platforms where @code{time_t} was
193 a fallback code is used with legacy (i.e. 32-bit) syscalls.
196 If @code{_TIME_BITS} is defined to be 32, @code{time_t} is defined to
198 as 32-bit @code{time_t} stops working in the year 2038.
204 @code{_TIME_BITS=64} can be defined only when
205 @code{_FILE_OFFSET_BITS=64} is also defined.
232 If you define this macro to the value @code{1}, features from ISO/IEC
265 @code{totalorder} functions and functions related to NaN payloads.
299 If this macro is defined, additional @code{*at} interfaces are
321 @code{_POSIX_C_SOURCE} with the value @code{199506L}.
324 for basic functionality (e.g.@: @code{getchar}) to be thread-safe.
327 We recommend you use @code{_GNU_SOURCE} in new programs. If you don't
330 explicitly, the effect is the same as defining @code{_DEFAULT_SOURCE}
335 those features. For example, if you define @code{_POSIX_C_SOURCE}, then
336 defining @code{_POSIX_SOURCE} as well has no effect. Likewise, if you
337 define @code{_GNU_SOURCE}, then defining either @code{_POSIX_SOURCE} or
338 @code{_POSIX_C_SOURCE} as well has no effect.