From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30714 invoked by alias); 21 Dec 2007 09:27:53 -0000 Received: (qmail 30705 invoked by uid 22791); 21 Dec 2007 09:27:52 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0910.google.com (HELO rv-out-0910.google.com) (209.85.198.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 21 Dec 2007 09:27:46 +0000 Received: by rv-out-0910.google.com with SMTP id g11so170402rvb.56 for ; Fri, 21 Dec 2007 01:27:43 -0800 (PST) Received: by 10.140.207.3 with SMTP id e3mr572314rvg.262.1198229263750; Fri, 21 Dec 2007 01:27:43 -0800 (PST) Received: by 10.141.195.16 with HTTP; Fri, 21 Dec 2007 01:27:43 -0800 (PST) Message-ID: Date: Fri, 21 Dec 2007 17:16:00 -0000 From: NightStrike To: "Ralf Wildenhues" Subject: Re: -Wparentheses lumps too much together Cc: gcc@gcc.gnu.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071219200235.GA21525@oak.schemamania.org> X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00646.txt.bz2 On 12/20/07, Ralf Wildenhues wrote: > freetds.org> writes: > > > > Yes, I know beginners get confused by and/or precedence. But > > *every* language that I know of that has operator precedence places > > 'and' before 'or'. > > FWIW, Bourne shell doesn't, && and || have equal precedence there. > That's a bit off-topic though, as it's not an argument against your > actual proposition, but rather one for `sh -Wall'. ;-) It's not entirely off-topic. Not all programmers are dedicated to a specific language. It's customary to work on several different languages, and keeping things like operator precedance straight in your head between languages is not always easy. Things like -Wall are a great help in making sure that you don't miss any of those inter-language oddities. As long as there are options to go either way, for instance: o -Wall checks by default, -Wno-parentheses disables o -Wall doesn't check by default, -Wparentheses enables then it's really just a question of what should be enabled by default, not what should be checked for at all. The point is... does it really matter, as long as everyone can go either way?