From owner-svn-src-head@FreeBSD.ORG Sun Nov 8 02:55:58 2009 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A1CB1065676 for ; Sun, 8 Nov 2009 02:55:58 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id ADBBC8FC0A for ; Sun, 8 Nov 2009 02:55:57 +0000 (UTC) Received: (qmail 29584 invoked by uid 399); 8 Nov 2009 02:55:57 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 8 Nov 2009 02:55:57 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AF63344.6080803@FreeBSD.org> Date: Sat, 07 Nov 2009 18:56:04 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Max Laier References: <200911020721.nA27LDq1048764@svn.freebsd.org> <4AEF22E3.5070701@freebsd.org> <200911021955.02459.max@love2party.net> In-Reply-To: <200911021955.02459.max@love2party.net> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Robert Watson , Colin Percival Subject: Re: svn commit: r198781 - head/lib/libc/sys X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2009 02:55:58 -0000 Max Laier wrote: > On Monday 02 November 2009 19:20:19 Colin Percival wrote: >> Robert Watson wrote: >>> On Mon, 2 Nov 2009, Colin Percival wrote: >>>> Attempt to reduce accidental foot-shooting by pointing out that >>>> accept(2)ed sockets do not necessarily inherit O_NONBLOCK from >>>> listening sockets on non-FreeBSD platforms. >>> I wonder how much trouble we should go to to document bugs in other >>> systems as non-portabilities for features that work in our system. >> I don't think there's any simple rule to apply here except "use common >> sense". One can argue that FreeBSD man pages exist for the purpose of >> documenting FreeBSD; but I'd also like to think that FreeBSD is a good >> development platform for writing portable applications, so alerting our >> users to potentially non-portable code certainly has some value. (And > > +1 ... FreeBSD is such a great development platform specifically because of > the complete man page collection. I'd argue, however, that we should keep the > portability notes to the fact that there might be a difference - without going > into too much detail what/where and why that difference is. In addition, the > more detail we add, the more likely it is that the information grows stale FWIW I agree here. Portability notes == good, details == bad; although I would include enough information in the notes so that an interested party can find the appropriate external reference(s). Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/