From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Cross <cross@math.psu.edu>
Message-Id: <200109051958.PAA04018@augusta.math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] weird print(2) problems...
In-Reply-To: <20010905184545.BA2EF19A3F@mail.cse.psu.edu>
Cc:
Date: Wed,  5 Sep 2001 15:58:36 -0400
Topicbox-Message-UUID: ea3f0496-eac9-11e9-9e20-41e7f4b1d025

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.