This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: typedef vs. typename confusion
- To: Joe Buck <jbuck at synopsys dot com>
- Subject: Re: typedef vs. typename confusion
- From: Jason Merrill <jason at cygnus dot com>
- Date: 06 Aug 1998 13:34:47 -0700
- Cc: nyap at garban dot com (Noel Yap), egcs at cygnus dot com
- References: <199808061940.MAA29430@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@Synopsys.COM> writes:
>> People should be able to specify a flag to compile older code. Did the
>> original compilers default to C behaviour (ie allowing use of
>> non-declared functions or assuming int when no type is specified)? I
>> don't think so, the compilers forced people to update their code, or
>> they supplied a switch that would allow older behaviour.
> Guess what g++ does? It allows use of non-declared functions, assuming
> int, and gives a warning. I think that it is time for this to go away,
> because it is now more trouble than it's worth
How so? There are still C libraries that people want to use with sloppy
declarations in the headers. I don't think this particular extension is
problematic.
> gcc has around a million users. You are one user. Your personal needs
> can be satisfied with "-pedantic" (at least, they could be if -pedantic
> were fixed).
Fixed?
Jason