All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Froyd <froydnj@codesourcery.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [7234] Use a more natural order
Date: Fri, 24 Apr 2009 11:58:57 -0700	[thread overview]
Message-ID: <20090424185857.GA22588@codesourcery.com> (raw)
In-Reply-To: <20090424180706.GR3795@csclub.uwaterloo.ca>

On Fri, Apr 24, 2009 at 02:07:06PM -0400, Lennart Sorensen wrote:
> On Thu, Apr 23, 2009 at 11:46:25PM +0100, Jamie Lokier wrote:
> > Sure, it was ok practice back in the days when compilers would let you
> > write "if (x = 0)", but those days are long gone.  Now all compilers
> > warn, and you can ask them to make it an error.  A compiler check is
> > much safer than depending on writing style, especially a weird one
> > that's inconsistent with other writing in the same code, and
> > inconsistent with English thinking.
> 
> I highly doubt all compilers warn.  Current gcc versions do, but not
> everyone uses current gcc.

Documentation indicates that the relevant warning (-Wparatheses) has
been supported since at least 2.95.3 (released early 2001); I imagine it
has been supported since the corresponding major release of 2.95.0
(released mid-1999).

-Nathan

  reply	other threads:[~2009-04-24 18:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:29 [Qemu-devel] [7234] Use a more natural order Blue Swirl
2009-04-23 18:39 ` Andreas Färber
2009-04-23 18:43   ` Blue Swirl
2009-04-23 18:53 ` Lennart Sorensen
2009-04-23 19:01   ` Blue Swirl
2009-04-23 19:10     ` Lennart Sorensen
2009-04-23 19:15       ` Glauber Costa
2009-04-23 19:39         ` Blue Swirl
2009-04-23 19:59           ` Anthony Liguori
2009-04-23 20:20             ` Blue Swirl
2009-04-23 19:57         ` Anthony Liguori
2009-04-23 19:59           ` Lennart Sorensen
2009-04-23 20:03             ` Anthony Liguori
2009-04-23 20:54               ` Lennart Sorensen
2009-04-23 21:15                 ` Anthony Liguori
2009-04-23 22:13                   ` Jamie Lokier
2009-04-24  0:10                     ` Anthony Liguori
2009-04-24  8:18                 ` Gerd Hoffmann
2009-04-24 12:14                   ` Anthony Liguori
2009-04-24 12:32                   ` Stefan Weil
2009-04-23 19:31       ` Blue Swirl
2009-04-23 19:44         ` Lennart Sorensen
2009-04-23 22:46           ` Jamie Lokier
2009-04-24 18:07             ` Lennart Sorensen
2009-04-24 18:58               ` Nathan Froyd [this message]
2009-04-23 19:12   ` M. Warner Losh
2009-04-23 19:28     ` Lennart Sorensen
2009-04-23 19:41       ` M. Warner Losh
2009-04-23 19:55         ` Lennart Sorensen
2009-04-23 20:07           ` M. Warner Losh
2009-04-23 21:01             ` Lennart Sorensen
2009-04-23 23:02           ` Jamie Lokier
2009-04-23 22:52       ` Jamie Lokier
2009-04-23 19:37   ` [Qemu-devel] " Jan Kiszka
2009-04-23 19:46     ` Lennart Sorensen
2009-04-23 21:30       ` malc
2009-04-23 22:10       ` Jamie Lokier
2009-04-24  8:09   ` [Qemu-devel] " Gerd Hoffmann

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=20090424185857.GA22588@codesourcery.com \
    --to=froydnj@codesourcery.com \
    --cc=blauwirbel@gmail.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.