public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: therapy@ripco.com (Blackbear)
To: help-gcc@gnu.org
Subject: Re: braces warning in DJGPP
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <82gfhm$5qu$1@gail.ripco.com> (raw)
Message-ID: <19991231222400.syTOqWsc7YGaD2YEjI7GO7XYu91PXS8eHcPtY5cd8L4@z> (raw)
In-Reply-To: <82er4c$b06$1@gail.ripco.com>

I've solved the problem. I looked at the compiler
souce to find "-Wno-missing-braces".

Blackbear (therapy@ripco.com) wrote:
: Hello everyone.

: I like to compile using the `-Wall' flag so that
: the compiler can catch possible errors for me. 

: For warnings that I don't want to see, I then
: put "-Wno-xxxxx" options after "-Wall" on
: the command line -- to turn off those warnings.

: But there is one warning that I can't disable. When I
: create a structure like so:

: struct decoder {
:         int             value;
:         const char *    name;
: };

: static struct decoder   basic_msgs [] = {
:         1,              "first",
:         2,              "second",
:         3,              "third",
:         .
:         .
:         .
: };

: The compiler issues a warning: 

: histbase.m:36: warning: missing braces around initializer
: histbase.m:36: warning: (near initialization for `basic_msgs[0]')

  reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-05 15:12 Blackbear
1999-12-06  6:04 ` Blackbear [this message]
1999-12-11 17:28   ` passing options through g++/gcc to linker Dave Topham
1999-12-31 22:24     ` Dave Topham
1999-12-31 22:24   ` braces warning in DJGPP Blackbear
1999-12-31 22:24 ` Blackbear

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='82gfhm$5qu$1@gail.ripco.com' \
    --to=therapy@ripco.com \
    --cc=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).