Date: Mon, 22 Jan 2001 09:32:18 -0600 From: "Jacques A. Vidrine" <n@nectar.com> To: Daniel Eischen <eischen@vigrid.com> Cc: Warner Losh <imp@harmony.village.org>, arch@FreeBSD.ORG Subject: Re: Request For Review: libc/libc_r changes to allow -lc_r Message-ID: <20010122093218.C93103@hamlet.nectar.com> In-Reply-To: <Pine.SUN.3.91.1010121145246.3245A-100000@pcnet1.pcnet.com>; from eischen@vigrid.com on Sun, Jan 21, 2001 at 03:04:43PM -0500 References: <200101211927.f0LJRU901079@harmony.village.org> <Pine.SUN.3.91.1010121145246.3245A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 21, 2001 at 03:04:43PM -0500, Daniel Eischen wrote: > On Sun, 21 Jan 2001, Warner Losh wrote: > > In message <Pine.SUN.3.91.1010120171614.8403A-100000@pcnet1.pcnet.com> Daniel Eischen writes: > > : > By the way, should it be __thread_sys_foo and __foo? Two underscores? > > : > ISTR some rule about using a single leading underscore for file scope > > : > (e.g. macros) and two for global scope. > > : > > : I don't recall that, but anything for file scope that isn't a macro > > : can be static and not use the underscores. Macros are usually upper > > : case anyways. > > > > ANSI C reserves _[A-Z]* and __[a-zA-Z] to the implementation space. > > That leaves _[a-z] to the user name space, so Jacques is right about > > that. > > Well, we don't seem to be following that right now, but I'll adhere to > that in anything I add. So how about instead of using _thread_sys_foo, > we use __sys_foo: > > __sys_foo - actual system call > _foo - weak definition to __sys_foo > foo - weak definition to __sys_foo Sounds good to me. __sys_foo is off-limits to the application. _foo will be file-scope only (no external linkage). Thanks! -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010122093218.C93103>