Date: Mon, 28 Jan 2008 11:55:29 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, David O'Brien <obrien@FreeBSD.org> 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 Message-ID: <86odb6usm6.fsf@ds4.des.no> In-Reply-To: <20080128053514.GK49535@comp.chem.msu.su> (Yar Tikhiy's message of "Mon\, 28 Jan 2008 08\:35\:15 %2B0300") 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Yar Tikhiy <yar@comp.chem.msu.su> 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. > 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. > 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. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86odb6usm6.fsf>