From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] sign extension a gogo,
Date: Wed, 16 Mar 2011 00:10:22 -0400 [thread overview]
Message-ID: <8c94ed5c284278d5fd2bce3fe6b918ff@brasstown.quanstro.net> (raw)
woe be unto he who abuses the right holy GBIT* macros with
signed integers; for verily will he be smitten by lust for sign
extension. i say unto you, he will be screwed.
(i'm looking at you devpnp.)
- erik
p.s. maybe a few ugly casts in the macros? it is quite a silly
bug. or heven forbid, make 'em functions?
reply other threads:[~2011-03-16 4:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8c94ed5c284278d5fd2bce3fe6b918ff@brasstown.quanstro.net \
--to=quanstro@quanstro.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).