This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

policy on __libc_*

To: GNU libc hacker <libc-hacker at sourceware dot cygnus dot com>
Subject: policy on __libc_*
From: Roland McGrath <roland at frob dot com>
Date: Wed, 5 Jan 2000 23:02:59 -0500

Regardless of the other bickering, I don't think I got a clear answer on
the question of what the general policy is about __libc_foo names.  I've
just __libc_ified lseek, open, and fcntl for the hurd since other things
have come to use those.  This is a non-issue for the hurd, since
cancellation is handled entirely differently (the __libc_foo, __foo, and
foo names are all aliases for the same thing regardless), but it would be
nice to know what to expect from the os-independent parts of libc.

Follow-Ups:
- Re: policy on __libc_*
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]