public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Chris Moller <cmoller@redhat.com>,
	tromey@redhat.com,         frysk <frysk@sourceware.org>
Subject: Re: TestCase.fail() bug
Date: Thu, 19 Apr 2007 13:57:00 -0000	[thread overview]
Message-ID: <462771FA.5060504@redhat.com> (raw)
In-Reply-To: <1176974393.4491.4.camel@dijkstra.wildebeest.org>

Mark, yes,

One of the more useful features of gcc is being able to cherry-pick the 
warnings.  For instance warn of unused locals, but not unused 
parameters.  Perhaps sun's front end is better at this?

Andrew

/me suffers a feeling of deja-vu

Mark Wielaard wrote:
>
> I better strategy would be to drop the -Wall, see what warnings remain
> and then add and/or disable specific warnings. For GNU Classpath we use
> the default and then disable the following:
> -warn:-deprecation,serial,typeHiding,unchecked,unused,varargsCast
> Some of these warnings are only disabled because they cannot be avoided
> when implementing the core libraries, so you might not want to disable
> all of them, but it might be a good start.
>
> Cheers,
>
> Mark
>
>   

  reply	other threads:[~2007-04-19 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 17:08 Chris Moller
2007-04-17 17:20 ` Chris Moller
2007-04-18 17:17 ` Andrew Cagney
2007-04-18 17:24   ` Chris Moller
2007-04-18 17:32     ` Phil Muldoon
2007-04-18 18:13       ` Chris Moller
2007-04-18 17:37     ` Nurdin Premji
2007-04-18 20:08     ` Tom Tromey
2007-04-19  3:02       ` Chris Moller
2007-04-19 13:16         ` Mark Wielaard
2007-04-19 13:57           ` Andrew Cagney [this message]
2007-04-19 14:17             ` Mark Wielaard
2007-04-24 12:46               ` Tom Tromey

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=462771FA.5060504@redhat.com \
    --to=cagney@redhat.com \
    --cc=cmoller@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.org \
    --cc=tromey@redhat.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).