From: Sergey Kish <sergey.kish@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /dev/draw and c, rc, ruby, python, go
Date: Mon, 11 Apr 2011 18:17:57 +0300 [thread overview]
Message-ID: <BANLkTin=pNBM3pd80DtiAnZSbysW7gOULQ@mail.gmail.com> (raw)
In-Reply-To: <20110411010934.GA14473@dinah>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Thanks! All implementations works now.
A typo fix in Go implementation was not enough. You can't write
message by parts, have to form it in buffer before writing.
ratrace helped to find problem with Ruby/Python implementations.
https://gist.github.com/912377#file_ratrace.log shows that both
writes to data after reading ctl. Fixed with a flush call.
> Also, you should really check the errors from any system call
> instead of discarding them.
It may be good in production, but in development I want program crash
as loud and quick as possible.
[-- Attachment #2: Type: text/html, Size: 810 bytes --]
prev parent reply other threads:[~2011-04-11 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 17:53 Sergey Kish
2011-04-10 20:49 ` ron minnich
2011-04-12 4:41 ` Akshat Kumar
2011-04-13 22:16 ` erik quanstrom
2011-04-11 0:49 ` Anthony Martin
2011-04-11 1:09 ` Anthony Martin
2011-04-11 15:17 ` Sergey Kish [this message]
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='BANLkTin=pNBM3pd80DtiAnZSbysW7gOULQ@mail.gmail.com' \
--to=sergey.kish@gmail.com \
--cc=9fans@9fans.net \
/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).