public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mike dot allen at facsim dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36696]  New: Default constructor instance definition with empty argument list quietly ignored
Date: Wed, 02 Jul 2008 14:25:00 -0000	[thread overview]
Message-ID: <bug-36696-16406@http.gcc.gnu.org/bugzilla/> (raw)

Compile following with -Wall:

#include <iostream>

class Raii
{
public:
    Raii () throw ()
    {
        std::cout << "Raii::Raii () called..." << std::endl;
    }
public:
    ~Raii () throw ()
    {
        std::cout << "Raii::~Raii () called..." << std:: endl;
    }
};

int main (int /*argc*/, char** /*argv*/)
{
    Raii raii ();
    std::cout << "Inside main ()..." << std::endl;
    return 0;
}

This compiles with no errors.  When the result is executed, you get the
following output:

Inside main ()...

And that's all.  The compiler quietly ignored the declaration of an Raii
instance with an empty argument list.  No warnings, no errors, nothing.

If the empty argument list is removed, that is, if you have:

#include <iostream>

class Raii
{
public:
    Raii () throw ()
    {
        std::cout << "Raii::Raii () called..." << std::endl;
    }
public:
    ~Raii () throw ()
    {
        std::cout << "Raii::~Raii () called..." << std:: endl;
    }
};

int main (int /*argc*/, char** /*argv*/)
{
    Raii raii;
    std::cout << "Inside main ()..." << std::endl;
    return 0;
}

Then you get the expected output:

Raii::Raii () called...
Inside main ()...
Raii::~Raii () called...

Is this correct behavior?

g++ -v:
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr
--enable-targets=all --enable-checking=release --build=i486-linux-gnu
--host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)


-- 
           Summary: Default constructor instance definition with empty
                    argument list quietly ignored
           Product: gcc
           Version: 4.2.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mike dot allen at facsim dot org
GCC target triplet: i486-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36696


             reply	other threads:[~2008-07-02 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 14:25 mike dot allen at facsim dot org [this message]
2008-07-02 14:42 ` [Bug c++/36696] " mike dot allen at facsim dot org
2008-07-02 21:10 ` dseketel at redhat dot com
2008-07-02 21:16 ` pinskia at gcc dot gnu dot org

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=bug-36696-16406@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).