From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] awk bug
Date: Mon, 15 Sep 2003 22:03:20 +0200 [thread overview]
Message-ID: <038601c37bc4$6a7eb0c0$b9844051@insultant.net> (raw)
In-Reply-To: <200309151144.h8FBiFuc032196@skeeve.com>
> This is a bug that was introduced when BWK switched from the lex scanner
> to a hand-written one. (Guess who told him about it? :-) It's fixed in
> the current version:
i understand that. i'd prefer to mangle the test scripts than to hack awk.
my reasoning being is that the side effects of hacking the test script are
minimal, but hacking awk is fraught with peril (i knew that before i bio-fied
it).
the rand() based tests are pretty much useless.
the problem is to make the right choice :(
next prev parent reply other threads:[~2003-09-15 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 9:53 boyd
2003-09-15 10:04 ` Geoff Collyer
2003-09-15 10:14 ` boyd, rounin
2003-09-15 11:44 ` Aharon Robbins
2003-09-15 20:03 ` boyd, rounin [this message]
2010-04-19 16:33 erik quanstrom
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='038601c37bc4$6a7eb0c0$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).