Re: [gentoo-user] Bash 3.2/3.1 compatibility?

Hi, 

I have the same problem and I was trying to solve it few weeks ago,
after almost two weeks of searching and compiling I substituted =~ with expr:

- orig use with ~= :
# if [[ "test" =~ ".*" ]]; then echo "ok"; fi

- alternative use with expr :
# export TEST_VAR="test"
# if [[ ${#TEST_VAR} == `expr "${TEST_VAR}" : ".*"` ]]; then echo "ok"; fi

It's more complicated, but it works. I also posted this as a bug with bashbug,
but no reply arrived. I hope this will help a little.

Jan

> ------------ Pùvodní zpráva ------------
> Od: Alex Schuster <wonko@×××××××××.org>
> Pøedmìt: Re: [gentoo-user] Bash 3.2/3.1 compatibility?
> Datum: 10.11.2007 04:14:19
> ----------------------------------------
> Willie Wong writes:
>
> > The situation:
> >   I have some bash scripts written. The scripts contains a lot of
> >   string comparisons. Perhaps my code was buggy before, perhaps it was
> >   not, but the change
> >
> >     "Quoting the string argument to the [[ command's  =~ operator now
> >     forces string matching, as with the other pattern-matching
> >     operators."
> >
> >   between 3.1->3.2 complete breaks my script.
>
> Yeah, I had the same problem. Very annoying.
>
>
> > The question:
> >
> >   Is there a switch that I can use to make bash run in some sort of
> >   compatibility mode for the string comparison? I.e, can I somehow
> >   force bash (in the script) to behave like before?
>
> I am pretty sure there is none. The suggested workaround is to put the
> string to be matched into a variable:
>
> <http://bashcurescancer.com/bash_faq_version_336_for_bash_version_32#SUB-E14>
>
> 	Wonko
> --
> gentoo-user@g.o mailing list
>
>
>
>
-- 
gentoo-user@g.o mailing list