From owner-freebsd-arch Mon Jan 22 7:32:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id B49BD37B401 for ; Mon, 22 Jan 2001 07:32:18 -0800 (PST) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 2774D193E4; Mon, 22 Jan 2001 09:32:18 -0600 (CST) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id f0MFWI093324; Mon, 22 Jan 2001 09:32:18 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Date: Mon, 22 Jan 2001 09:32:18 -0600 From: "Jacques A. Vidrine" To: Daniel Eischen Cc: Warner Losh , arch@FreeBSD.ORG Subject: Re: Request For Review: libc/libc_r changes to allow -lc_r Message-ID: <20010122093218.C93103@hamlet.nectar.com> References: <200101211927.f0LJRU901079@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eischen@vigrid.com on Sun, Jan 21, 2001 at 03:04:43PM -0500 X-Url: http://www.nectar.com/ Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 03:04:43PM -0500, Daniel Eischen wrote: > On Sun, 21 Jan 2001, Warner Losh wrote: > > In message 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