This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: C++ PATCH: functional cast
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: C++ PATCH: functional cast
- From: Jason Merrill <jason at cygnus dot com>
- Date: 17 Sep 1999 11:47:00 -0700
- Cc: nathan at cs dot bris dot ac dot uk, nathan at acm dot org, egcs-patches at egcs dot cygnus dot com
- References: <37E200E9.2625E7C@acm.org> <19990917082307U.mitchell@codesourcery.com>
>>>>> Mark Mitchell <mark@codesourcery.com> writes:
>>>>> "Nathan" == Nathan Sidwell <nathan@acm.org> writes:
Nathan> Hi, attached is a patch to parse.y dealing with the `const
Nathan> (3)' extension to functional style cast. We accept that
Nathan> under the implicit int rule, but currently do not issue a
Nathan> diagnostic. This patch uses groktypename so it goes
> I think we should just not accept that. It's time for implicit int to
> go. But, Jason may feel differently.
I see no reason to keep this instance of implicit int, but I think Nathan's
patch will result in a better error message.
Nathan> NB. The comma expression extension in `int (x,y)' is
Nathan> undocumented -- can we remove it?
> I'd be happy to. Ask Jason.
Again, I think the message in build_functional_cast is more useful than a
syntax error. It's not an feature if it gets an unconditional pedwarn.
Jason