Bug#358831: bash operand errors (forwarded from C.Y.M)

2006-04-18 Thread C.Y.M
C.Y.M wrote:
 Chet Ramey wrote:
 Matthias Klose wrote:
 C.Y.M writes:
 Reverting back to bash 3.0 fixes the problem.  It seems bash 3.1 has 
 broken the
 way the arrays are read.
 Once again bitten by using a too-general function for consistency
 across different expansions :-).

 I will be releasing a patch for this.
 
 
 Excellent.  Thank you for taking the time to look at this.
 

This problem is now fixed with bash31-017.  Thank you.

BR.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#358831: bash operand errors (forwarded from C.Y.M)

2006-03-31 Thread Chet Ramey
Matthias Klose wrote:
 C.Y.M writes:
 Reverting back to bash 3.0 fixes the problem.  It seems bash 3.1 has broken 
 the
 way the arrays are read.

Once again bitten by using a too-general function for consistency
across different expansions :-).

I will be releasing a patch for this.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
   Live Strong.  No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#358831: bash operand errors (forwarded from C.Y.M)

2006-03-31 Thread C.Y.M
Chet Ramey wrote:
 Matthias Klose wrote:
 C.Y.M writes:
 Reverting back to bash 3.0 fixes the problem.  It seems bash 3.1 has broken 
 the
 way the arrays are read.
 
 Once again bitten by using a too-general function for consistency
 across different expansions :-).
 
 I will be releasing a patch for this.


Excellent.  Thank you for taking the time to look at this.

BR.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]