177
178 These functions have been standardized by POSIX. However, the 64-bit
179 variants, ntohll(3C) and htonll(3C) are not standardized and may not be
180 found on other systems. For more information on these functions, see
181 byteorder(3C).
182
183 The second family of functions, endian(3C), provide a means to convert
184 between the host's byte order and big-endian and little-endian
185 specifically. While these functions are similar to those in
186 byteorder(3C), they more explicitly cover different data conversions.
187 Like them, these functions operate on either 16-bit, 32-bit, or 64-bit
188 values. When converting from big-endian, to the host's endianness, the
189 functions begin with betoh. If instead, one is converting data from the
190 host's native endianness to another, then it starts with htobe. When
191 working with little-endian data, the prefixes letoh and htole convert
192 little-endian data to the host's endianness and from the host's to
193 little-endian respectively.
194
195 These functions are not standardized and the header they appear in varies
196 between the BSDs and GNU/Linux. Applications that wish to be portable,
197 shoulda instead use the byteorder(3C) functions.
198
199 All of these functions in both families simply return their input when
200 the host's native byte order is the same as the desired order. For
201 example, when calling htonl(3C) on a big-endian system the original data
202 is returned with no conversion or modification.
203
204 SEE ALSO
205 byteorder(3C), endian(3C), endian.h(3HEAD), inet(3HEAD)
206
207 illumos August 2, 2018 illumos
|
177
178 These functions have been standardized by POSIX. However, the 64-bit
179 variants, ntohll(3C) and htonll(3C) are not standardized and may not be
180 found on other systems. For more information on these functions, see
181 byteorder(3C).
182
183 The second family of functions, endian(3C), provide a means to convert
184 between the host's byte order and big-endian and little-endian
185 specifically. While these functions are similar to those in
186 byteorder(3C), they more explicitly cover different data conversions.
187 Like them, these functions operate on either 16-bit, 32-bit, or 64-bit
188 values. When converting from big-endian, to the host's endianness, the
189 functions begin with betoh. If instead, one is converting data from the
190 host's native endianness to another, then it starts with htobe. When
191 working with little-endian data, the prefixes letoh and htole convert
192 little-endian data to the host's endianness and from the host's to
193 little-endian respectively.
194
195 These functions are not standardized and the header they appear in varies
196 between the BSDs and GNU/Linux. Applications that wish to be portable,
197 should instead use the byteorder(3C) functions.
198
199 All of these functions in both families simply return their input when
200 the host's native byte order is the same as the desired order. For
201 example, when calling htonl(3C) on a big-endian system the original data
202 is returned with no conversion or modification.
203
204 SEE ALSO
205 byteorder(3C), endian(3C), endian.h(3HEAD), inet(3HEAD)
206
207 illumos August 2, 2018 illumos
|