public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gccbugs@contacts.eelis.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/10416: 'unused variable' warning ignores ctor/dtor side-effects
Date: Tue, 15 Apr 2003 18:56:00 -0000	[thread overview]
Message-ID: <20030415184711.19743.qmail@sources.redhat.com> (raw)


>Number:         10416
>Category:       c++
>Synopsis:       'unused variable' warning ignores ctor/dtor side-effects
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 15 18:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Eelis van der Weegen
>Release:        gcc 3.2
>Organization:
>Environment:

>Description:
Sometimes a variable is created only for the side-effects of its constructor/destructor. For example, in the following code:

struct Closer { ~Closer() { CloseClipboard(); } } closer;

the closer variable is only used to make sure the clipboard is closed when the function leaves (normally or exceptionally).

G++ apparently does not think this is valid use of a variable, and warns: "warning: unused variable".
>How-To-Repeat:
Compile:

void f () { struct atend { ~atend () { std::cout << "leaving f\n"; } } a; }

with -Wall.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-15 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 18:56 gccbugs [this message]
2003-04-16 23:15 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=20030415184711.19743.qmail@sources.redhat.com \
    --to=gccbugs@contacts.eelis.net \
    --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: 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).