On Mon, Jan 13, 2003 at 12:42:24PM -0800, Terry Lambert wrote: > > > > Some configure scripts may check for <floatingpoint.h> for compatibility > > with SunOS/Solaris. I doubt they will check <machine/floatingpoint.h> > > And here's the reason why. The SPARC platform for FreeBSD will need > to be sensitive to the fact that people will port from SPARC running > some other OS to SPARC running FreeBSD. The most likely source of > ported code in this case is SPARC running Solaris, which has the > header file in question.
Ok. I'm now going to throw (an interpretation of) your own words into the mix and let you decide how you want to prioritize them. You said that FreeBSD on different platforms should not cause variation in the API or ABI. If having <floatingpoint.h> on sparc64 makes sense, then having all kinds of proprietary OS quirks on platforms with proprietary OSes also makes sense. This contradicts with the uniformity across platforms. Either we present the FreeBSD ABI and API uniformly across the supported platforms or we provide an uniform subset and allow deviation for ease of porting but then also have to accept porting across different FreeBSD implementations. I favor an uniform ABI/API if only to keep our ports meisters sane, but also because there's just too much difference that the existence or non-existence of <floatingpoint.h> will not make a big difference in porting SunOS/Solaris code. This is gut-feeling -- use salt... -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
