In article <[EMAIL PROTECTED]> Uriel wrote:
>Don't complain, at least it is not producing random behaviour, I have
>seen versions of gnu awk that when feed plain ASCII input, if the
>locale was UTF-8, rules would match random lines of input, the fix?
>set the locale to 'C' at the top of all your scripts (and don't even
>think of dealing with files which actually contain non-ASCII UTF-8).
>
>This was some years ago, it might be fixed by now, but it demonstrates
>how the locale insanity makes life so much more fun.
It likely is fixed by now. If not, I'd like to have a sample program and
data and locale name to test under. And the truth is, even if it doesn't work,
I can blame the library routines and locale and not my code. :-)
Testing should be performed using current sources, available via anonymous
CVS from savannah.gnu.org, check out the gawk-stable module. From CVS use:
./bootstrap.sh
./configure && make && make check
to build on a Unix or Linux system.
I hope to make a formal release in the next few weeks.
As to the original thread, yeah, configure (= autoconf + automake +
libtool + gnulib) has gotten way too hairy to handle. I don't use gnulib
on principle: I have the gut feeling that the configuration goop would
likely outweigh the source code in line count.
The only reason I added Automake support was to get GNU Gettext, which
on balance is a good thing. Locales, on the other hand, I think are
very painful. I hope that people who use them find them valuable (I'm
a parochial English speaking American myself, so ASCII is usually
enough for me.)
My two cents,
Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381 Fax: +1 206 202 4333
Nof Ayalon Cell Phone: +972 50 729-7545
D.N. Shimshon 99785 ISRAEL
