public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44499] No default constructor available Date: Fri, 11 Jun 2010 11:12:00 -0000 [thread overview] Message-ID: <20100611111148.28359.qmail@sourceware.org> (raw) In-Reply-To: <bug-44499-17090@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from manu at gcc dot gnu dot org 2010-06-11 11:11 ------- Comeau C/C++ 4.3.10.1 (Oct 6 2008 11:28:09) for ONLINE_EVALUATION_BETA2 Copyright 1988-2008 Comeau Computing. All rights reserved. MODE:strict errors C++ C++0x_extensions "ComeauTest.c", line 9: error: const variable "g_d" requires an initializer -- class "D" has no explicitly declared default constructor const D g_d; ^ "ComeauTest.c", line 9: warning: variable "g_d" was declared but never referenced const D g_d; ^ 1 error detected in the compilation of "ComeauTest.c". I think the error message of comeau is better (but our note is better). I will write a patch. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44499
next prev parent reply other threads:[~2010-06-11 11:12 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-11 9:10 [Bug c++/44499] New: " piotr dot wyderski at gmail dot com 2010-06-11 9:26 ` [Bug c++/44499] " redi at gcc dot gnu dot org 2010-06-11 10:28 ` redi at gcc dot gnu dot org 2010-06-11 10:53 ` manu at gcc dot gnu dot org 2010-06-11 11:01 ` piotr dot wyderski at gmail dot com 2010-06-11 11:12 ` manu at gcc dot gnu dot org [this message] 2010-06-11 11:12 ` manu at gcc dot gnu dot org 2010-06-11 11:14 ` manu at gcc dot gnu dot org 2010-07-02 8:09 ` manu at gcc dot gnu dot org 2010-07-02 8:12 ` pluto at agmk dot net 2010-07-02 9:15 ` manu at gcc dot gnu dot org [not found] <bug-44499-4@http.gcc.gnu.org/bugzilla/> 2011-03-03 22:28 ` dirtyepic at gentoo dot org 2011-03-03 23:14 ` redi at gcc dot gnu.org 2011-03-03 23:16 ` redi at gcc dot gnu.org 2011-03-04 10:02 ` manu at gcc dot gnu.org 2011-03-04 11:23 ` redi at gcc dot gnu.org 2011-03-04 11:25 ` redi at gcc dot gnu.org 2011-03-17 11:46 ` dirtyepic at gentoo dot org 2011-03-17 11:46 ` redi at gcc dot gnu.org 2011-03-19 20:05 ` redi at gcc dot gnu.org 2011-09-25 14:39 ` paolo.carlini at oracle dot com 2014-02-16 10:02 ` jackie.rosen at hushmail dot com
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=20100611111148.28359.qmail@sourceware.org \ --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: 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).