From: EBo <ebo@sandien.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] writing to ctl using fprint and write
Date: Thu, 29 Jul 2010 09:27:56 -0600 [thread overview]
Message-ID: <07d76da82c98729a30df3c13ae0e1766@swcp.com> (raw)
In-Reply-To: <764fc0b0ab4cc1f9a890bc61a61a7c81@ladd.quanstro.net>
> relax. not stupid, subtle. it takes vigilance to keep
> sizeof, nelem, strlen, and the number of characters
> straight.
I was not offended or anything. I spent WAY to much time missing on that
one before asking for another set of eyes. I just felt a bit foolish for
missing something that simple, and yes it is a subtle error. That's all.
The funny thing is that I had it reading correctly using sizeof(some
struct), and then blew it when I was writing a string. Anyway, it all
works now.
I really do appreciate the catch.
EBo --
next prev parent reply other threads:[~2010-07-29 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 12:02 EBo
2010-07-29 12:06 ` erik quanstrom
2010-07-29 13:21 ` EBo
2010-07-29 15:04 ` erik quanstrom
2010-07-29 15:11 ` David Leimbach
2010-07-29 23:42 ` Federico G. Benavento
2010-07-29 15:18 ` Brian L. Stuart
2010-07-29 15:27 ` EBo [this message]
2010-07-29 12:07 ` Skip Tavakkolian
2010-07-29 12:12 ` Sape Mullender
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=07d76da82c98729a30df3c13ae0e1766@swcp.com \
--to=ebo@sandien.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).