From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] remember when C compiler used to produce working code? i don't!
Date: Sat, 31 Jan 2004 02:34:22 +0100 [thread overview]
Message-ID: <045601c3e79a$5c234120$67844051@SOMA> (raw)
In-Reply-To: <027401c3e796$68040370$8201a8c0@cc77109e>
> indeed. the expression is being rewritten as
>
> elasticity *= (long)ratio;
sure looked like it.
next prev parent reply other threads:[~2004-01-31 1:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 22:05 andrey mirtchovski
2004-01-30 22:29 ` David Presotto
2004-01-30 22:40 ` David Presotto
2004-01-31 0:57 ` Bruce Ellis
2004-01-31 1:34 ` boyd, rounin [this message]
2004-01-31 1:51 ` Bruce Ellis
2004-01-31 2:15 ` boyd, rounin
2004-01-31 3:13 ` David Presotto
2004-01-31 7:40 ` Bruce Ellis
2004-01-31 9:03 ` andrey mirtchovski
2004-01-31 10:08 ` David Tolpin
2004-01-31 14:19 ` boyd, rounin
2004-01-31 14:57 ` Bruce Ellis
2004-01-31 17:59 ` Scott Schwartz
2004-01-31 19:23 ` Rob Pike
2004-01-31 19:59 ` Bruce Ellis
2004-01-31 20:42 ` Charles Forsyth
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='045601c3e79a$5c234120$67844051@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/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).