From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] simplicity
Date: Tue, 9 Oct 2007 22:08:20 +0200 [thread overview]
Message-ID: <200710092008.l99K8KZV004052@skeeve.com> (raw)
In-Reply-To: <5d375e920709180838t4070c23al11bc0eb5cc7280c9@mail.gmail.com>
In article <5d375e920709180838t4070c23al11bc0eb5cc7280c9@mail.gmail.com> 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
next prev parent reply other threads:[~2007-10-09 20:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:55 Francisco J Ballesteros
2007-09-16 20:42 ` Anant Narayanan
2007-09-16 21:24 ` Francisco J Ballesteros
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-16 20:43 ` roger peppe
2007-09-16 20:53 ` Steve Simon
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-17 20:00 ` Scott Schwartz
2007-09-17 3:23 ` erik quanstrom
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-17 15:55 ` erik quanstrom
2007-09-18 8:38 ` Douglas A. Gwyn
2007-09-18 10:45 ` dave.l
2007-09-18 14:44 ` Iruata Souza
2007-09-18 15:41 ` Douglas A. Gwyn
2007-09-18 21:34 ` Iruata Souza
2007-10-10 3:30 ` Jack Johnson
2007-10-10 4:02 ` erik quanstrom
2007-10-10 6:17 ` Jack Johnson
2007-10-10 12:22 ` erik quanstrom
2007-09-18 15:27 ` Rob Pike
2007-09-18 15:38 ` Uriel
2007-09-19 8:50 ` Douglas A. Gwyn
2007-09-19 11:51 ` erik quanstrom
2007-09-19 15:02 ` Russ Cox
2007-09-19 14:17 ` Charles Forsyth
2007-09-19 14:21 ` Iruata Souza
2007-09-19 15:32 ` Skip Tavakkolian
2007-10-09 20:08 ` Aharon Robbins [this message]
2007-10-09 21:08 ` Uriel
2007-10-10 5:33 ` sqweek
2007-10-10 11:49 ` erik quanstrom
2007-09-17 14:52 ` ron minnich
2007-09-17 14:53 ` ron minnich
2007-10-10 7:36 John Stalker
2007-10-10 8:24 ` Charles Forsyth
2007-10-10 11:47 ` erik quanstrom
2007-10-10 14:05 ` John Stalker
2007-10-10 14:29 ` erik quanstrom
2007-10-10 15:26 ` John Stalker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710092008.l99K8KZV004052@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).