From kde-devel Wed Oct 27 13:32:31 2004 From: Thiago Macieira Date: Wed, 27 Oct 2004 13:32:31 +0000 To: kde-devel Subject: Re: Byte order conversions Message-Id: <200410271032.31747.thiago.macieira () kdemail ! net> X-MARC-Message: https://marc.info/?l=kde-devel&m=109888487806858 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1170080154==" --===============1170080154== Content-Type: multipart/signed; boundary="nextPart2161640.e5lafBPsVh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2161640.e5lafBPsVh Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Szombathelyi Gy=F6rgy wrote: >> htons, htonl, ntohs, ntohl should do the big-endian to machine-endian >> stuff. > >Then why these functions are not used? Is there any portabiliy issues? I could guess that the reasons are: 1) people don't know they exist 2) people don't want to #include #include #include just to have them (unlike glibc on Linux, some systems out there require that you include the= =20 dependencies yourself) 3) people require little-endian to host-endian conversions Aside from that, they are mandated to exist by sockets, so I don't believe= =20 there are portability issues. =2D-=20 Thiago Macieira - Registered Linux user #65028 thiago (AT) macieira (DOT) info ICQ UIN: 1967141 PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 --nextPart2161640.e5lafBPsVh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBBf6NvM/XwBW70U1gRAl6qAKCXwyRVBz9oJVobiC4Tig/hC9eRMACgrtXa tuxwY8a6hRT5Lgn8P4d/1FE= =ZyGw -----END PGP SIGNATURE----- --nextPart2161640.e5lafBPsVh-- --===============1170080154== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============1170080154==--