From: Kastil <lordgalloth@gmail.com>
To: "Eljay Love-Jensen" <eljay@adobe.com>, GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: Description warnings
Date: Thu, 31 Jul 2008 15:33:00 -0000 [thread overview]
Message-ID: <op.ue5ld50lt61k1h@galloth> (raw)
In-Reply-To: <C4B7064E.7825%eljay@adobe.com>
On Thu, 31 Jul 2008 13:03:58 +0200, Eljay Love-Jensen <eljay@adobe.com>
wrote:
> Hi Jan,
>
> To get a definitive list, using grep (or perl or your favorite
> text-scraping
> tool) on the GCC source code (for the version of GCC you are interested
> in)
> would be one way to produce a reliably complete list of warnings.
>
> HTH,
> --Eljay
>
Hi,
I was hoping for something which will describe these warnings. Some think
that will tell me what I have done wrong in my program and why gcc
produced this warning.
Now when gcc writes me some warning I spend a lot of time trying to figure
out, what I have done wrong (or what could be done better). I am looking
for something that could reduce this time.
Thank for your answer.
Jan
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2008-07-31 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 11:12 Kastil
2008-07-31 11:31 ` Eljay Love-Jensen
2008-07-31 15:33 ` Kastil [this message]
2008-07-31 17:07 ` Brian Dessent
2008-08-02 13:52 Eus
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=op.ue5ld50lt61k1h@galloth \
--to=lordgalloth@gmail.com \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.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 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).