On Tue, 2006-02-28 at 20:35 -0600, I wrote:
> echo ${BIGSTRING} | sed "s/^.*\($MYSTRING\).*$/\\${COUNTER}/"
>
> The word "string" was returned, as expected.
>
> JUSTFORBRUCE=`echo ${BIGSTRING} | sed "s/^.*\($MYSTRING\).*$/\\${COUNTER}/"`
>
> echo $JUSTFORBRUCE
>
> Woops, we didn't get what we wanted. We got ${COUNTER} instead
Now that I think about it further, I still consider `...` broken. Here's
why:
It works one way when not used assigning a variable and works completely
different when using *exactly the same syntax* to assign it to a
variable.
To me, this inconsistency is broken behavior.
--
Randy
rmlinux: [bogomips 3993.32] [GNU ld version 2.16.1] [gcc (GCC) 4.0.2]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
12:01:59 up 1 day, 19:13, 7 users, load average: 0.21, 0.10, 0.09
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
