9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] weird print(2) problems...
Date: Wed,  5 Sep 2001 15:58:36 -0400	[thread overview]
Message-ID: <200109051958.PAA04018@augusta.math.psu.edu> (raw)
In-Reply-To: <20010905184545.BA2EF19A3F@mail.cse.psu.edu>

In article <20010905184545.BA2EF19A3F@mail.cse.psu.edu> you write:
>Kind of, but there's a special case either way.
>If you're generating morse code I'd use bio anyway,
>and then you don't have to worry about 0-length writes.

That (bio) sounds like the right solution for the morse code program,
which is actually a pipeline.  This program just generates random code
groups to be sent to another program that translates them into dots and
dashes, and then another reads that and translates it into a ``tones''
little language which is read by yet another program that generates PCM
sounds samples; the output of all that is finally directed into the
audio device.

But, having a program that does a `print("");' render an acme window
unusable for all intents and purposes still seems like a problem that
needs to be fixed somehow.

	- Dan C.



  reply	other threads:[~2001-09-05 19:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 18:40 Russ Cox
2001-09-05 19:58 ` Dan Cross [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-11 11:16 rob pike
     [not found] <rsc@plan9.bell-labs.com>
2001-09-05 21:11 ` Russ Cox
2001-09-05 21:24   ` Scott Schwartz
2001-09-05 19:46 Russ Cox
2001-09-05 19:19 Russ Cox
2001-09-05 19:40 ` Boyd Roberts
2001-09-06  8:19 ` Matthew Hannigan
2001-09-06 16:18 ` Douglas A. Gwyn
2001-09-06 20:45   ` Boyd Roberts
2001-09-05 15:11 forsyth
2001-09-05 18:23 ` Dan Cross
2001-09-05 19:10   ` Boyd Roberts
     [not found] <cross@math.psu.edu>
2001-09-04 19:02 ` Dan Cross
2001-09-04 19:08   ` Scott Schwartz
2001-09-05 14:22     ` Dan Cross
2001-09-05 19:01       ` Boyd Roberts

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=200109051958.PAA04018@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).