From owner-freebsd-sparc Tue Jan 14 1:47:24 2003 Delivered-To: freebsd-sparc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6B9D37B401 for ; Tue, 14 Jan 2003 01:47:22 -0800 (PST) Received: from excalibur.skynet.be (excalibur.skynet.be [195.238.3.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 876BC43F3F for ; Tue, 14 Jan 2003 01:47:21 -0800 (PST) (envelope-from trollet@skynet.be) Received: from skynet.be (163.248-136-217.adsl.skynet.be [217.136.248.163]) by excalibur.skynet.be (8.11.6/8.11.6/Skynet-OUT-2.20) with ESMTP id h0E9lGd22430 for ; Tue, 14 Jan 2003 10:47:16 +0100 (MET) (envelope-from ) Message-ID: <3E23D8EE.DDA28DBB@skynet.be> Date: Tue, 14 Jan 2003 10:31:26 +0100 From: Atle X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.9 sun4u) X-Accept-Language: no, en MIME-Version: 1.0 Cc: sparc@FreeBSD.ORG Subject: Re: [PATCH] Re: fpsetmask on sparc64 References: <20030113034638.GA2310@dhcp01.pn.xcllnt.net> <20030113190710.I11541-100000@gamplex.bde.org> <20030113100558.GA3423@dhcp01.pn.xcllnt.net> <3E2324B0.585FD417@mindspring.com> <20030113210642.GB798@dhcp01.pn.xcllnt.net> <3E232F9C.D323FF99@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > Having on SPARC makes sense, in terms of being > able to support a *legacy* interface for *legacy* code that needs > it. Both uses of the word "legacy" are important here. I think > that the header file should complain, during compilation, when it > is used, e.g.: > > #warning "this file includes which is obsoleted, use > instead" > > This doesn't contradict uniformity across platforms, per se, > since the interface is deprecated. Please excuse an ignorant fool for barging in, I have been following this, taken a step back, and concluded 'this is not easy to follow'. I often consult my wife when I have design problems, so I will be the 'wife' here. I try as far as possible to let names be uniform across declaration (.h files) and libraries (.a .o .so). So if a program does this #include then it links with something called foo.o or libfoo.a Anything that depends on i386 lives inside some #ifdef i386 #include <386quirks.h> #else #include #endif Is there a fundamental design issue here? If there is even a change that some circular #includes can happen, then surely there must be something wrong? Please ignore this if it is irrelevant, Atle http://atle.linux-site.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message