From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] is there any good reason why awk does this?
Date: Wed, 3 Sep 2003 08:56:52 -0400 [thread overview]
Message-ID: <b7c439f3159eb62cbfc4633d38fa86d9@plan9.bell-labs.com> (raw)
In-Reply-To: <01cb01c37215$c5a7e420$b9844051@insultant.net>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
I think you're wrong. The only occurrence of /dev/std* in the source
is in a table that makes them work in awk programs. That is,
awk 'BEGIN {print "hello world" >"/dev/stderr" }'
works because of that table. It's not a bug.
[-- Attachment #2: Type: message/rfc822, Size: 2361 bytes --]
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] is there any good reason why awk does this?
Date: Wed, 3 Sep 2003 14:20:28 +0200
Message-ID: <01cb01c37215$c5a7e420$b9844051@insultant.net>
> Frobbing exit[s] (and making it grok UTF-8?) are not evil designs on life,
> the universe, and everything.
it will behave just like it does now on plan 9 except you can go:
exit "foo"
now testing it is probably going to be a bugger.
i did find this bug:
/dev/std* were being used instead of /fd/*
next prev parent reply other threads:[~2003-09-03 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 2:50 boyd
2003-09-01 7:01 ` Charles Forsyth
2003-09-01 13:53 ` boyd, rounin
2003-09-01 17:35 ` rob pike, esq.
2003-09-02 0:38 ` boyd, rounin
2003-09-01 17:41 ` Joel Salomon
2003-09-01 17:37 ` Dan Cross
2003-09-03 0:33 ` boyd, rounin
2003-09-03 8:48 ` Douglas A. Gwyn
2003-09-03 9:31 ` Lyndon Nerenberg
2003-09-03 12:20 ` boyd, rounin
2003-09-03 12:56 ` Russ Cox [this message]
2003-09-03 21:19 ` boyd, rounin
2003-09-03 22:15 ` boyd, rounin
2003-09-03 13:30 ` Ralph Corderoy
2003-09-03 21:18 ` boyd, rounin
2003-09-08 9:09 ` Ralph Corderoy
2003-09-08 9:53 ` boyd, rounin
2003-09-03 12:08 ` boyd, rounin
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=b7c439f3159eb62cbfc4633d38fa86d9@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).