This is the mail archive of the
mailing list for the glibc project.
Re: GNU libio vs. GNU stdio.
- To: firstname.lastname@example.org
- Subject: Re: GNU libio vs. GNU stdio.
- From: Mark Kettenis <email@example.com>
- Date: Sat, 9 Jan 1999 20:15:52 +0100 (CET)
- CC: firstname.lastname@example.org, email@example.com
- References: <m0zz1Wo-00038dC@ocean.lucon.org>
From: firstname.lastname@example.org (H.J. Lu)
Date: Sat, 9 Jan 1999 08:46:22 -0800 (PST)
The only reason I know that GNU stdio is still in glibc is Hurd doesn't
support libio. Otherwise it would have been removed from glibc long
time ago. BTW, how hard to fix Hurd for libio? As far as I know, stdio
may have more bugs than libio. I don't see why we should keep it in
The idea is to switch to libio when the Hurd pthreads implementation
has been finished, because both changes will break binary
compatibility, and using versioning to overcome these problems is too
hairy. Another problem that the Hurd exec server depends heavily on
GNU stdio internals.
AFAIK it used to be possible to use GNU stdio together with the native
stdio (with some appropriate glue). This was necessary since GNU libc
was intended to be a drop-in replacement for the native libc. But
this probably doesn't work anymore.