public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gonz@ratloop.com To: gcc-gnats@gcc.gnu.org Subject: c/9049: No support for selective enabling/disabling of warnings Date: Mon, 23 Dec 2002 16:26:00 -0000 [thread overview] Message-ID: <20021224001747.27987.qmail@sources.redhat.com> (raw) >Number: 9049 >Category: c >Synopsis: No support for selective enabling/disabling of warnings >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Mon Dec 23 16:26:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Pete Gonzalez >Release: 3.2.1 >Organization: >Environment: Debian Linux >Description: GCC provides no facility for disabling/enabling a warning for a single function or block of code. Every other C/C++ compiler has this feature. Examples: Visual C++: #pragma warning Borland C++: #pragma warn Watcom C++: #pragma warning Here is some sample syntax in Visual C++: int a; #pragma warning( disable : 4705 ) // diable warning void func() { a; } #pragma warning( default : 4705 ) // restore original setting GCC has no such feature, requiring warnings to be disabled globally for an entire file (or project). >How-To-Repeat: N/A >Fix: Implement the "warning" pragma. Or, provide GCC attributes for disabling/enabling warnings. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-24 0:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-23 16:26 gonz [this message] 2003-01-08 2:48 bangerth
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=20021224001747.27987.qmail@sources.redhat.com \ --to=gonz@ratloop.com \ --cc=gcc-gnats@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: linkBe 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).