From: Jason Mancini <jayrusman@hotmail.com>
To: <jwakely.gcc@gmail.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: infinite for-loop and related question
Date: Wed, 16 Feb 2011 21:37:00 -0000 [thread overview]
Message-ID: <SNT106-W38A844009B0AB5C1712FDCABD20@phx.gbl> (raw)
In-Reply-To: <AANLkTim=BeKq2wpiVs3DeouVqAc-QrgtnvSUSWSFRCZN@mail.gmail.com>
> No. The C and C++ standards define that unsigned integers do not
> overflow, they wrap, with well-defined behaviour.
Aha, thank you!
Though I still find the output of this odd:
for (char i(1); i>0; ++i)
printf("%d %d\n", i, sizeof(i));
...
362195 1
362196 1
362197 1
...
For very large values of char! ^_^
Jason
next prev parent reply other threads:[~2011-02-16 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 20:17 Jason Mancini
2011-02-16 20:41 ` Jonathan Wakely
2011-02-16 21:37 ` Jason Mancini [this message]
2011-02-16 21:49 ` Bob Plantz
2011-02-16 23:00 ` Jonathan Wakely
2011-02-16 23:22 ` Thomas Martitz
2011-02-17 6:31 ` Jonathan Wakely
2011-02-17 10:36 ` Axel Freyn
2011-02-17 12:23 ` Jonathan Wakely
2011-02-17 13:16 ` Axel Freyn
2011-02-17 14:08 ` Jonathan Wakely
2011-02-16 23:00 Bill McEnaney
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=SNT106-W38A844009B0AB5C1712FDCABD20@phx.gbl \
--to=jayrusman@hotmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).