Bruce Evans wrote: > On Sun, 12 Jan 2003, Terry Lambert wrote: > > This patch also affects the IA64 and Alpha, as well as just the SPARC. > > > > It took a lot of discussion, but it seems to me that the problem is > > that the prototypes in scope aren't in scope when the wrong include > > file is included. > > Right. It is mainly an application bug like I said. The prototypes > also aren't in scope when <stdio.h> is included, and the fix is not > to add them to <stdio.h>.
I really disagree. A legacy application *can't* be said to be buggy. If someone cuts you off, and you get into an accident, it was the fault of the person who cut you off, not you. If a legacy application stops working because a system changes, it's the fault of the system doing the changing, not the fault of the people back in 1984 who didn't know ANSI was going to bung-up the C language until their application no longer worked. There has to be some allowance for the continuity of code; it can't just be orphaned instantaneously, without some warning from the system vendor. Say we took your approach, and moved the #define's for the inlines up into <ieeefp.h>, exposing platform dependencies in a (supposedly) platform independent header file. How many ports would break? All of the ports that won't compile on Alpha or SPARC or IA64 today, will end up not compiling on i386, either. That's not an acceptable thing, right before the 5.0 release. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
