Re: emerge of ksh93 erroring out.. who can interpret

6 msg	KDE4 overlay
2 msg	x11-drm fails to emerge
2 msg	gentoo-dev
7 msg	Gentoo LiveUSB
3 msg	External ISDN modem
6 msg	Ebuilds for additional campaigns for games-stra...
162 msg	Is GWN dead?
16 msg	Routing problem ?
3 msg	Enigmail in Thunderbird 2.0.0.9
5 msg	VMware Server Tools
2 msg	[OT] stable non-anonymous free http proxy
13 msg	Update After A Year
14 msg	Kernel setting for frame buffer (2.6.23-r5)
18 msg	What's with this hald thing and why can't I rip...
11 msg	package.provided
3 msg	digraph error while trying to emerge
11 msg	FreeAgent extn. Drive setup ideas
14 msg	Incredibly slow disk access

emerge of ksh93 erroring out.. who can interpret
\ Harry Putnam (7 Jan 2008)
. \ Alan McKinnon (8 Jan 2008)
. \ reader (9 Jan 2008)
. . \ Matthias B. (10 Jan 2008)
. \ reader (11 Jan 2008)
. . \ Matthias B. (11 Jan 2008)
. \ reader (11 Jan 2008)
. . \ Matthias B. (11 Jan 2008)
. . \ Alex Schuster (14 Jan 2008)
. \ reader (14 Jan 2008)
. . \ Alex Schuster (14 Jan 2008)

3 msg	postfix with TLS

Subject:	Re: emerge of ksh93 erroring out.. who can interpret
Group:	Gentoo-user
From:	Alex Schuster
Date:	14 Jan 2008

reader writes:

> Alex Schuster <wonko> writes:
>
>> reader writes:

> But I was really just saying that syntax at my low level of usage is
> largely interchangeable but for the cases I mentioned. So it makes
> switching scripting shells from ksh93 to bash pretty smooth.

Well, good luck then :)

> Something for your consideration I learned on comp.unix.shell that
> ksh93 can handle associative arrays where as bash cannot or maybe just
> not as easily. The example given by Icarus S. there for ksh93 was:
[...]

> You may find that discussion interesting

Yeah, this is one of the things I would also like very much to have. But the
Bash FAQ (<http://tiswww.case.edu/php/chet/bash/FAQ>) not only states that
bash lacks this feature (C2), but also says that this is planned for the
future (H3). So I wait and hope it will happen soon. Well. Eventually.

>> The other problem was with the =~ notation and quoting of the regular
>> expression not being allowed any more. Workaround is to define a variable
>> (foo) with the expression: [[ "blabla" =~ $foo ]]
>
> I can't reproduce that here (I mean a problem with quoting the regex)
> but maybe I'm not getting what you mean? Or maybe its been fixed.
[...]

In bash < 3.2, [[ 1 =~ "1|2|3" ]] worked and evaluated to true, but
[[ 1 =~ 1|2|3 ]] gave a syntax error. In bash >= 3.2, [[ 1 =~ "1|2|3" ]]
does not match any longer, only [[ 1 =~ 1|2|3 ]] does. The workaround is to
define a variable foo, and use [[ 1 =~ $foo ]].

Wonko
--
gentoo-user mailing list