public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: bridean@ameritech.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/5517: Internal variables in classes not stored correctly
Date: Mon, 28 Jan 2002 16:38:00 -0000	[thread overview]
Message-ID: <20020129003834.9208.qmail@sources.redhat.com> (raw)

Synopsis: Internal variables in classes not stored correctly

State-Changed-From-To: open->closed
State-Changed-By: rodrigc
State-Changed-When: Mon Jan 28 16:38:33 2002
State-Changed-Why:
    This is not a bug in the compiler, but a bug in your program.
    
    Look at your mult() function:
    
    Polynomial Polynomial::mult(double num)
    {
      printf("Current polynomial is: ");
      this->print();
      Polynomial ans(degree);
      printf("Current polynomial is: ");
      this->print();
      int i;
     
      for (i=degree; i>=0; i--)
        {
          ans.coeff[i] = num * coeff[i];
          printf("coeff[i] is: %0.12lf\n", coeff[i]);
        }
      return ans;
    }
    
    
    Your are creating a Polynomial on the stack and then
    returning it.  But when the scope of the mult() function
    ends, the destructor will be called on ans!
    
    If you gave your class a Polynomial a copy constructor,
    and did something like:
       return Polynomial(ans);
    
    you would be OK.
    
    This is not a gcc bug.  Refer to a good C++ book,
    or ask questions on the comp.lang.c++.moderated newsgroup.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5517


             reply	other threads:[~2002-01-29  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 16:38 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-28 12:46 bridean

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=20020129003834.9208.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=bridean@ameritech.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).