X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: [ANNOUNCEMENT] Updated [experimental]: readline-5.2-2,  libreadline6-5.2-2 - Bash-3.2-3
Date: Thu, 19 Oct 2006 14:15:52 +0000 (UTC)
Lines: 31
Message-ID:  <loom.20061019T160746-357@post.gmane.org>
References:  <Pine DOT OSF DOT 4 DOT 21 DOT 0610191553110 DOT 13405-100000 AT ax0rm1 DOT roma1 DOT infn DOT it>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Angelo Graziosi <Angelo.Graziosi <at> roma1.infn.it> writes:

> 
> 
> The combination 
> 
>    Bash-3.2-3+readline/libreadline6-5.2-2
> 
> seems to solve the problems described in
> http://cygwin.com/ml/cygwin/2006-10/msg00642.html.
> 
> The problems still remain if one uses bash-3.1-9.

Then it sounds like an upstream limitation and not a bash specific problem, 
where in the process of adding new hooks to readline 5.2 and using those new 
hooks in bash 3.2, the upstream maintainer inadvertantly broke the semantics of 
the old hooks in use by bash 3.1 (in other words, he kept the shared library 
binary compatible, but not behaviorally compatible).  If it bothers you enough, 
then you should report it upstream (bug-bash AT gnu.org), and see if the 
upstream maintainer would patch readline 5.2 to avoid breaking programs that 
linked against readline 5.1.  But since I won't be promoting readline 5.2 to 
current without also promoting bash 3.2, it doesn't bother me enough to worry 
about it unless someone were to report a program other than bash 3.1 that was 
also affected by this change in the semantics.  Bash tends to be the most 
extreme user of all the hooks and knobs provided by the readline library; most 
readline clients don't exercise all those knobs, and therefore don't care when 
a hook added primarily for bash changes in semantics.

-- 
Eric Blake



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/