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]

Re: policy on __libc_*

To: Roland McGrath <roland at frob dot com>
Subject: Re: policy on __libc_*
From: Ulrich Drepper <drepper at cygnus dot com>
Date: 05 Jan 2000 20:36:15 -0800
Cc: GNU libc hacker <libc-hacker at sourceware dot cygnus dot com>
References: <200001060402.XAA10058@frob.com>
Reply-To: drepper at cygnus dot com (Ulrich Drepper)

Roland McGrath <roland@frob.com> writes:

> but it would be nice to know what to expect from the os-independent
> parts of libc.

You are right, that would be nice.  But I really have no time to write
this all down in detail.  I think I've explained on the list a few
times already that the __libc_* names are introduced for cancelation
points since the functions must be intercepted even when called from
inside the libc.  I.e., the __* functions also have to be exported.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com   `------------------------

Follow-Ups:
- Re: policy on __libc_*
  - From: Roland McGrath

References:
- policy on __libc_*
  - From: Roland McGrath

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