Re: -Wno-return-type doesn't seem to work.

[Dirk Zoller <duz at rtsffm dot com>]

Hello Martin,

while I understand and share your anger about Sun for being incredibly
sloppy in keeping their system up to standards, I think you are not
acting logically in this minor point. Reasons:

1) When the option -Wno-return-type is completely ineffective, then
   why does it exist?

> So, you should complain to your operating system vendor about not
> conforming to international standards, instead of to your compiler
> vendor for doing so.

2) Agreed. But when you are beginning to stop taking care about the
   problems caused by the imperfect world of vendor-Unices, then what
   does this line in the source:

	  if (in_system_header)
	    /* Allow it, sigh.  */;

   Certainly sigh! But my point is that the following lines you got
   your if-conditions a little wrong.

3) When the new direction of gcc is to enforce standard behaviour to
   the rest of the world, then there should be no need for fixinclude.
   Otherwise fixinclude might also be a place where this long standing
   problem might be avoided.

> If you absolutely can't live with the warning: Well, you got the
> source to both the compiler, and the X11 headers.

I'd change that when you include the fix in the next release. I always
thought that's why I have the source: To fix or improve something and
share that. Not in order to be able to fix it again and again. Though
you may refuse to call this deviation from standards a "fix".


/usr/include/*.h has always been and will always be the greatest
source of frustration to the unix programmer working on many
platforms. IMHO.

Regards
Dirk

-- 
Dirk Zoller					e-mail	duz@rtsffm.com
Gruppe RTS Realtime Systems			Phone	+49 69 61009 324
Rembrandtstr. 13				Fax	+49 69 61009 181
60596 Frankfurt (Germany)