From: James Tomaschke <james@orcasystems.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Unexpected 8c warning message
Date: Tue, 11 Aug 2009 15:16:43 -0700 [thread overview]
Message-ID: <4A81EDCB.5090800@orcasystems.com> (raw)
In-Reply-To: <20090811113013.8513221d.eekee57@fastmail.fm>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ethan Grammatikidis wrote:
> I just don't like parsing a for statement, it's rarely clear and usually ugly to my eyes.
Writing a parser to parse a for statement is slightly more involved as
well. However I was commenting on how the compiler seems to handle a
do/while properly so it might be possible to get for- and while-loops to
avoid reporting the false warning with some effort.
I still use for(;;) instead of while(1) ever since I saw compilers emit
machine code that moved $1 into a register followed by a compare. Most
modern compilers do no do this anymore but old habits die hard.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqB7csACgkQl3JZTBu3/9lgjACgsrd39mxz4Ak6x9cY4iUeK0+A
gnUAnRwbVd/6nkxLW5dtxeoxJnS+Njf/
=Rkj5
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-08-11 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 19:33 Adriano Verardo
2009-08-09 19:46 ` Russ Cox
2009-08-09 21:20 ` Adriano Verardo
2009-08-09 21:48 ` erik quanstrom
2009-08-10 16:24 ` Adriano Verardo
2009-08-10 16:43 ` erik quanstrom
2009-08-10 17:19 ` Russ Cox
2009-08-10 23:30 ` Adriano Verardo
2009-08-11 0:19 ` Charles Forsyth
2009-08-10 20:33 ` Adriano Verardo
2009-08-10 21:01 ` James Tomaschke
2009-08-11 10:30 ` Ethan Grammatikidis
2009-08-11 22:16 ` James Tomaschke [this message]
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=4A81EDCB.5090800@orcasystems.com \
--to=james@orcasystems.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).