echo foo | sed 's/$/BAR/'
give "foo" instead of fooBAR (which we all know is the only reasonable
answer). So, I pulled GNU sed-2.05 off the net, compiled it, and
about two dozen warnings later got a binary that worked correctly for
the above case. After some more investigation, it turned out that
"sed" shows the same behavior as my old binary *if* I link it against
the rx library in libc. I tried the same Spiel on a Linux/x86 box:
same result: sed works with its own rx library but fails to match $
properly when linked against the rx library in libc.
So here are my questions:
1) Does anybody know why my old sed binary apparently got linked
against the rx library in libc? (My guess is that my binary
comes from one of the BLADE sets, but it might also come from
grocne.)
2) Are there any known (64-bit related) problems in the rx library
that comes with GNU sed-2.05? (I think that version is identical
with GNU librx-0.05.)
3) Is there any reason *not* to replace the rx library in libc with
the GNU version?
--david