From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] weird print(2) problems...
From: "Russ Cox" <rsc@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010905211114.7A030199DD@mail.cse.psu.edu>
Date: Wed,  5 Sep 2001 17:11:10 -0400
Topicbox-Message-UUID: ea43a6fe-eac9-11e9-9e20-41e7f4b1d025

> 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.

We've overloaded a read of length 0 with
two meanings, and there's no good way out now.
Should write(1, "", 0) render an acme window
unusable?  Maybe it's acme's fault.  Telnetd waits
for three zero-length writes, so that
	g% echo -n
dosen't hang up the connection but
	g% echo -n; echo -n; echo -n
still does.  We can dive into heuristics
ad nauseum, but I think we're just stuck
with the overload until everyone switches
to a language with tupled return values
like Limbo.

Russ