From: Branko Cibej <branko.cibej@hermes.si>
To: Carlo Wood <carlo@runaway.xs4all.nl>
Cc: "egcs@cygnus.com" <egcs@cygnus.com>
Subject: Re: Desire gcc option to skip warnings in standard headers
Date: Tue, 30 Jun 1998 00:42:00 -0000 [thread overview]
Message-ID: <35988F6B.69CB713C@hermes.si> (raw)
In-Reply-To: <199806291617.SAA24744@jolan.ppro>
Carlo Wood wrote:
> A #pragma seems more logical, and more flexible too.
>
> Other compilers allow to turn off each type of
> warning seperately with a #pragma, which would be
> the ideal. It would introduce a boolean for each type
> of warning, and I imagine we need an array for that:
> An array that contains these variables, and the warnings
> and some code that is used.
Och aye, I know a certain compiler that does that. The feature is used widely in the
rather broken libraries shipped with said compiler...
Anyway, I agree with Jeff that #pragmas are not the way to go. One does want to
write portable code once in a while.[skip some very non-egcs-ish example code]
> ...
>
> Doesn't that look nice? :)
Beautiful, and I'm sure you'd be willing to spend some time to modify egcs in this
manner :->
--
Branko Cibej <branko.cibej@hermes.si>
HERMES SoftLab, Litijska 51, 1000 Ljubljana, Slovenia
phone: (++386 61) 186 53 49 fax: (++386 61) 186 52 70
next prev parent reply other threads:[~1998-06-30 0:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-26 13:03 Frederick W. Wheeler
1998-06-29 8:41 ` Branko Cibej
1998-06-29 8:41 ` Carlo Wood
1998-06-29 8:41 ` Branko Cibej
1998-06-29 20:41 ` Carlo Wood
1998-06-30 0:00 ` Jeffrey A Law
1998-06-30 9:03 ` Andi Kleen
1998-07-01 0:54 ` Carlo Wood
1998-06-30 23:15 ` Mumit Khan
1998-07-01 20:15 ` Raja R Harinath
1998-06-30 0:42 ` Branko Cibej [this message]
1998-06-30 0:42 ` Jeffrey A Law
1998-06-30 9:03 ` Branko Cibej
1998-06-29 9:38 ` Branko Cibej
[not found] <9806261352.AA18188.cygnus.egcs@ipl.rpi.edu>
1998-07-01 20:15 ` Nathan Myers
1998-07-04 12:40 ` Joseph H. Buehler
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=35988F6B.69CB713C@hermes.si \
--to=branko.cibej@hermes.si \
--cc=carlo@runaway.xs4all.nl \
--cc=egcs@cygnus.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).