public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: BrainChild@Skyler.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/9666: Arg conversion problem with operator new Date: Fri, 14 Feb 2003 21:22:00 -0000 [thread overview] Message-ID: <20030214212228.23352.qmail@sources.redhat.com> (raw) Synopsis: Arg conversion problem with operator new State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Fri Feb 14 21:22:28 2003 State-Changed-Why: Confirmed -- well, sort of, since I am not sure whether this is legal. Here's the code slightly reformatted: ------------------------- #include <cstddef> struct X { operator size_t (); operator size_t () const; }; char *f2 (const X &x) { return new char[x]; } -------------------------- The compiler complains: tmp/g> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc: In function `char* f2(const X&)': x.cc:8: error: expression in new-declarator must have integral or enumeration type Now, I tend to think that the code is illegal, due to 5.3.4.7: 7 Every constant-expression in a direct-new-declarator shall be an inte- gral constant expression (_expr.const_) and evaluate to a strictly positive value. The expression in a direct-new-declarator shall have integral type (_basic.fundamental_) with a non-negative value. Then, on the other hand, this code compiles: ----------------------- #include <cstddef> struct X { /* operator size_t (); */ operator size_t () const; }; char *f2 (const X &x) { return new char[x]; } ----------------------- I should think that the presence of the second non-const operator shouldn't make a difference since x is a constant reference... Can someone clarify? W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9666
next reply other threads:[~2003-02-14 21:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-14 21:22 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-11 20:46 BrainChild
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=20030214212228.23352.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=BrainChild@Skyler.com \ --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: 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).