From owner-cvs-all@FreeBSD.ORG Mon Jan 28 16:13:05 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9848C16A418; Mon, 28 Jan 2008 16:13:05 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id EE8A013C467; Mon, 28 Jan 2008 16:13:04 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0SGD1Yq006862; Mon, 28 Jan 2008 19:13:01 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0SGD1Tt006861; Mon, 28 Jan 2008 19:13:01 +0300 (MSK) (envelope-from yar) Date: Mon, 28 Jan 2008 19:13:00 +0300 From: Yar Tikhiy To: Dag-Erling Sm??rgrav Message-ID: <20080128161300.GP49535@comp.chem.msu.su> References: <200801261709.m0QH9f2D024309@repoman.freebsd.org> <20080127043334.GA75235@dragon.NUXI.org> <20080127053813.GH49535@comp.chem.msu.su> <20080127094653.GA74753@dragon.NUXI.org> <20080128053514.GK49535@comp.chem.msu.su> <86odb6usm6.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86odb6usm6.fsf@ds4.des.no> User-Agent: Mutt/1.5.9i Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, David O'Brien Subject: Re: cvs commit: src UPDATING src/include fts.h src/lib/libc/gen Makefile.inc Symbol.map fts-compat.c fts-compat.h fts.3 fts.c src/sys/sys param.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2008 16:13:05 -0000 On Mon, Jan 28, 2008 at 11:55:29AM +0100, Dag-Erling Sm??rgrav wrote: > Yar Tikhiy writes: > > Excuse me, but did you notice that fts(3) is not a part of sys? It's > > generic userland code, albeit it's contaminated by system-dependent > > parts for performance or whatever. > > Irrelevant. Says who? > > But let intN_t be mostly confined in the kernel and system-dependent > > userland code. E.g., system-dependent include files can use them > > to define more portable types such as ino_t, nlink_t, or whatever. > > C99 doesn't define those either. POSIX does. But please stop catching me by my tongue and concentrate on the real essence of the issue. > > Userland code should be portable and useful to other systems in the > > chosen domain of compatibility, e.g., C99 or POSIX, unless there > > are substantial reasons for it not to. That's how different projects > > can benefit from each other's work. > > Both C99 and POSIX *require* int64_t and uint64_t on all platforms that > have 64-bit integer types. > > FreeBSD has never run on any platform that doesn't. I don't think > NetBSD or OpenBSD has either, nor Solaris, nor Linux to my knowledge. How long ago did you read the Ten C Commandments? You may want to refer to the last of them. -- Yar