From mboxrd@z Thu Jan  1 00:00:00 1970
From: Francisco J Ballesteros <nemo@lsub.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-Id: <8DAE8251-7C0C-4940-849B-C18AFDCCEE54@lsub.org>
Date: Mon, 18 Feb 2013 16:21:49 +0100
To: 9fans@9fans.net
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [9fans] two questions about go in Plan 9
Topicbox-Message-UUID: 195e9e90-ead8-11e9-9d60-3106f5b1d025

Forgive me,=20

Somehow I removed the -v from the call to go test. That makes the log =
print only for failed tests.

Regarding TCP, forsyth reminded me that it's what I'd get with the std. =
Plan 9 system calls, which
is so.

I guess my question is=85 how can I interrupt a reader in that case? In =
C I'd be able to interrupt it.
Now, in go on Plan 9, I can't interrupt it and I can't make the stream =
hangup.=20

What do you do in that case? Or, more likely, what am I doing wrong?

thanks


On Feb 18, 2013, at 4:07 PM, nemo@lsub.org wrote:

> Hi,
>=20
> I've been using go for a few things in Plan 9, and noticed a couple of =
things.
> I'd just like to know if it's me or if this also happens to others:
>=20
> - diagnostics issued by log.Print et al. don't show up unless I call =
log.Fail
> - closing a tcp connection which is still open by a nearby reader proc =
does not report EOF to the other end
> of the connection.
>=20
> It might be something I made or something I didn't understand, but =
just in case=20
> these are known I thought I might ask here.
>=20
> thanks=20
>=20
>=20
> [/mail/box/nemo/msgs/201302/876]