Maintaining libio

Florian Weimer fweimer@redhat.com
Wed Apr 19 13:23:00 GMT 2017


On 04/19/2017 03:17 PM, Dmitry V. Levin wrote:
> On Wed, Apr 19, 2017 at 03:01:25PM +0200, Florian Weimer wrote:
>> On 04/19/2017 02:35 PM, Dmitry V. Levin wrote:
>>> On Wed, Apr 19, 2017 at 11:17:21AM +0200, Florian Weimer wrote:
>>> [...]
>>>> I'm leaning towards a clean break: Stop installing <libio.h>.
>>>
>>> You must be joking.  This would definitely break libzio.
>>
>> I'm not.
>>
>> I just tried, and libzio 1.04 compiles fine with !HAVE_LIBIO_H.  It
>> doesn't define its own vtables, either, nor does it internal _IO_* symbols.
> 
> libzio uses cookie_io_functions_t provided by libio.h;
> in case of !HAVE_LIBIO_H it falls back to _IO_cookie_io_functions_t
> also defined by libio.h via stdio.h;
> 
> If stdio.h continues to provide fopencookie and _IO_cookie_io_functions_t,
> this should be enough for libzio.

The documented type of the fopencookie argument is 
cookie_io_functions_t, and we will continue to provide that from 
<stdio.h> (if _GNU_SOURCE is defined).

Thanks,
Florian



More information about the Libc-alpha mailing list