This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Future of libio vtable compatibility

From: Florian Weimer <fw at deneb dot enyo dot de>
To: Carlos O'Donell <carlos at redhat dot com>
Cc: libc-alpha at sourceware dot org
Date: Tue, 19 Jun 2018 21:11:40 +0200
Subject: Re: Future of libio vtable compatibility
References: <87h8m41oa0.fsf@mid.deneb.enyo.de> <3a215566-1748-a095-8bfa-c5c1d5017156@redhat.com> <874li0uig3.fsf@mid.deneb.enyo.de> <bcd031d0-3b1a-b404-9731-36179ed06446@redhat.com> <87efh3u9vo.fsf@mid.deneb.enyo.de> <6d8c852f-30e2-50f3-b846-0fdd1ad33a9f@redhat.com> <878t7bu834.fsf@mid.deneb.enyo.de> <80e0f086-a966-618d-7b27-1f42a7b9a5c9@redhat.com>

* Carlos O'Donell:

>>> But given the dubious value of the libio vtable compat, I think we
>>> should be deprecating it in a future release.
>> 
>> We alread did that in glibc 2.27.
>
> We removed the public symbols, but we haven't really touched the vtable
> layout?

We deprecated.  We didn't make any real changes.

Follow-Ups:
- Re: Future of libio vtable compatibility
  - From: Carlos O'Donell

References:
- Future of libio vtable compatibility
  - From: Florian Weimer
- Re: Future of libio vtable compatibility
  - From: Carlos O'Donell
- Re: Future of libio vtable compatibility
  - From: Florian Weimer
- Re: Future of libio vtable compatibility
  - From: Carlos O'Donell
- Re: Future of libio vtable compatibility
  - From: Florian Weimer
- Re: Future of libio vtable compatibility
  - From: Carlos O'Donell

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