From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4A81EDCB.5090800@orcasystems.com> Date: Tue, 11 Aug 2009 15:16:43 -0700 From: James Tomaschke User-Agent: Thunderbird 2.0.0.22 (X11/20090707) MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <4A7F246E.8000504@tecmav.com> <4A808A92.1000800@orcasystems.com> <20090811113013.8513221d.eekee57@fastmail.fm> In-Reply-To: <20090811113013.8513221d.eekee57@fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Unexpected 8c warning message Topicbox-Message-UUID: 42a616aa-ead5-11e9-9d60-3106f5b1d025 -----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-----