From: Chet Ramey <chet.ramey@case.edu>
To: Yury Gribov <y.gribov@samsung.com>,
Pedro Alves <palves@redhat.com>,
Doug Evans <dje@google.com>
Cc: chet.ramey@case.edu, bug-readline@gnu.org,
Vyacheslav Barinov <v.barinov@samsung.com>,
Yury Usishchev <y.usishchev@samsung.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [Bug-readline] [PATCH] Enable visibility annotations
Date: Wed, 20 Apr 2016 15:30:00 -0000 [thread overview]
Message-ID: <5717A080.7010403@case.edu> (raw)
In-Reply-To: <57176010.6060100@samsung.com>
On 4/20/16 3:55 AM, Yury Gribov wrote:
>> The alternative is bless the private symbols as
>> public API forever... Each package owner will know what their
>> package needs from readline and why they found a need
>> to (ab)use readline private symbols. I see no way around that.
>
> Guess that's what's going to happen (unless some motivated readline
> maintainer steps in, willing to work with various users on getting rid of
> leaked symbols).
I can work with people as my time permits, as long as they contact me.
I'm going to look at the visibility patches for the next bash/readline
release, but it's too late to get them into bash-4.4/readline-7.0.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2016-04-20 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 18:16 Doug Evans
2016-04-20 6:02 ` Yury Gribov
2016-04-20 9:22 ` Pedro Alves
2016-04-20 9:45 ` Yury Gribov
2016-04-20 10:19 ` Pedro Alves
2016-04-20 10:55 ` Yury Gribov
2016-04-20 15:30 ` Chet Ramey [this message]
2016-04-20 21:16 ` Chet Ramey
2016-04-22 14:43 ` Pedro Alves
2016-04-22 15:25 ` Chet Ramey
[not found] <570F38DD.1030703@samsung.com>
[not found] ` <570F3C7E.30005@samsung.com>
[not found] ` <570F7554.7070901@redhat.com>
[not found] ` <570FB04D.2060107@case.edu>
2016-04-14 15:19 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5717A080.7010403@case.edu \
--to=chet.ramey@case.edu \
--cc=bug-readline@gnu.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=v.barinov@samsung.com \
--cc=y.gribov@samsung.com \
--cc=y.usishchev@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox