From: John Love-Jensen <eljay@adobe.com>
To: Nelson Guedes Paulo Junior <npaulo@linux.ime.usp.br>
Cc: "Andrea 'Fyre Wyzard' Bocci" <fwyzard@inwind.it>,
snodx@hotmail.com, gcc-help@gcc.gnu.org
Subject: Re: IP ADDRESS OF MACHINE
Date: Thu, 28 Feb 2002 06:49:00 -0000 [thread overview]
Message-ID: <3C7E38FB.794E2217@adobe.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0202281037300.5877-100000@jacuzzi.linux.ime.usp.br>
Hi Nelson,
Change the one line to...
typedef unsigned char byte;
printf ("address: %hhu.%hhu.%hhu.%hhu\n", \
(*entry)[0] & 0xFF,
(*entry)[1] & 0xFF,
(*entry)[2] & 0xFF,
(*entry)[3] & 0xFF);
What you are seeing is an octet being treated as signed, and the signed
extension value being displayed as an unsigned int.
The mask will slice the sign extended high-bits off properly.
--Eljay
next prev parent reply other threads:[~2002-02-28 14:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 9:17 snodx
2002-02-27 19:32 ` Andrea 'Fyre Wyzard' Bocci
2002-02-28 6:03 ` Nelson Guedes Paulo Junior
2002-02-28 6:49 ` John Love-Jensen [this message]
2002-02-28 10:15 ` Nelson Guedes Paulo Junior
2002-03-01 6:34 ` John Love-Jensen
2002-03-05 1:07 ` Bharathi S
[not found] <616BE6A276E3714788D2AC35C40CD18D53345D@whale.softwire.co.uk>
2002-03-05 1:18 ` Rupert Wood
[not found] <616BE6A276E3714788D2AC35C40CD18D47C245@whale.softwire.co.uk>
2002-02-28 5:39 ` Rupert Wood
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 4:04 snodx
2002-02-28 4:30 ` Michal Lipták
2002-02-28 3:56 snodx
2002-02-28 3:25 snodx
2002-02-28 3:55 ` Edmund Green
[not found] <616BE6A276E3714788D2AC35C40CD18D47C203@whale.softwire.co.uk>
2002-02-28 2:43 ` Rupert Wood
2002-02-28 1:38 snodx
2002-02-27 5:13 snodx
2002-02-26 18:29 Robert Lopez
2002-02-26 4:18 snodx
2002-02-26 5:46 ` Stephano Mariani
2002-02-28 14:02 ` Florian Weimer
2002-02-26 0:35 snodx
2002-02-26 1:29 ` Frank Schafer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7E38FB.794E2217@adobe.com \
--to=eljay@adobe.com \
--cc=fwyzard@inwind.it \
--cc=gcc-help@gcc.gnu.org \
--cc=npaulo@linux.ime.usp.br \
--cc=snodx@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).