From owner-freebsd-hackers Tue Jan 11 10:56:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 233CD14E52 for ; Tue, 11 Jan 2000 10:56:18 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 2810 invoked by uid 1001); 11 Jan 2000 18:56:12 -0000 Date: Tue, 11 Jan 2000 10:56:12 -0800 From: Jason Evans To: "Richard Seaman, Jr." Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Adding alternate entry points to libc (was Re: Possible libc changes to support LinuxThreads) Message-ID: <20000111105612.B302@sturm.canonware.com> References: <19991209003517.E73529@sturm.canonware.com> <19991209064256.B34152@tar.com> <20000111103527.A302@sturm.canonware.com> <20000111124932.E360@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000111124932.E360@tar.com>; from dick@tar.com on Tue, Jan 11, 2000 at 12:49:32PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 12:49:32PM -0600, Richard Seaman, Jr. wrote: > On Tue, Jan 11, 2000 at 10:35:27AM -0800, Jason Evans wrote: > > The naming > > approach I'm taking is: > > > > fwrite() <-- Alternate entry point that is used externally unless > > another library overrides it. > > _libc_fwrite() <-- `_libc_' prefix. Alternate entry point for internal > > library use. > > __fwrite() <-- `__' prefix. Actual name. > > > > The reason for a prefix of `__' instead of `_' in the actual name case is > > that using only one underscore would be ambiguous at least in the cases of > > setjmp()/_setjmp() and longjmp()/_longjmp(). > > FYI, the actual name with a single '_' is already defined for syscalls via > SYS.h. Aliasing '__sycall' to '_syscall' is ok, I assume. Or, are you planning > on replacing the '_syscall's? Setjmp/_setjmp are libc calls but not syscalls. > I'm under the impression that linux glibc uses both single and double underscore > symbols, but I don't recall exactly what distinction they make between the two. It would be more consistent to change to `__' for syscalls, but I was planning on leaving the syscalls with `_', and adding `__' aliases, for fear that changing it would violate some "law of libc". Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message