From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7 <xconq7@sources.redhat.com>, xconq-hackers@lists.sourceforge.net
Subject: Re: How long was *that* there, I wonder?
Date: Sat, 04 Dec 2004 12:40:00 -0000 [thread overview]
Message-ID: <41B149C2.2030902@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0412032356210.14151@opal.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> because I thought it was obvious what it did. You call it
> with coordinates and a parameter 1 to set a bit, and you call it with
> coordinates and a parameter 0 to clear a bit. Right?
One would think.
> I'm not sure of the moral of the story - maybe "It's a good idea to trace
> down into those low-level functions once in a while". For such a simple
> bug, this one soaked up a lot of debugging hours.
Well, I'm glad you caught and fixed your bug. There is still something
nasty lurking in my modified 'see_cell' code, and I still haven't caught it.
Eric
prev parent reply other threads:[~2004-12-04 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 5:23 mskala
2004-12-04 12:40 ` Eric McDonald [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=41B149C2.2030902@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq-hackers@lists.sourceforge.net \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).