9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sleep-complexity
Date: Sun,  8 May 2005 22:12:35 +0100	[thread overview]
Message-ID: <8dc25d6e6eb4100818b09a511477f06e@terzarima.net> (raw)
In-Reply-To: <20050508172815.GA29137@augusta.math.psu.edu>

>> because long and int are the same so it really doesn't matter.

>That's not a terribly great assumption to make, is it?

the assumption usually made in practice is a little more subtle:
int <= long[=32] < long long [=64].  most older programs tended
to use int for things such as for loop values, that probably needed to be
at least 16 bits, but might not need to be as much as 32.
by contrast, a `long' quite often needed to be 32 bits, and often
that was `no more, no less'.

it's historically consistent and works well enough.
u32int etc are used a bit more these days, but not
exclusively.

the other subtle assumptions concern pointers and integers.
as it happens, the best choice there is happily consistent with dhog's, although
he didn't face that problem in his alpha port.  it does need source
code changes, but with care, they tend to be fairly limited, outside the kernel.



  parent reply	other threads:[~2005-05-08 21:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 12:03 Christoph Lohmann
2005-05-08 12:51 ` Sergey Reva
2005-05-08 16:50   ` Russ Cox
2005-05-08 17:28     ` Dan Cross
2005-05-08 18:56       ` jmk
2005-05-08 19:21         ` Bruce Ellis
2005-05-08 20:54           ` Charles Forsyth
2005-05-08 21:06             ` Charles Forsyth
2005-05-08 22:40         ` Dan Cross
2005-05-08 22:59           ` geoff
2005-05-09  7:28             ` Richard Miller
2005-05-09 13:14             ` Brantley Coile
2005-05-09 16:45             ` Mike Haertel
2005-05-09 20:10               ` Bruce Ellis
2005-05-09 22:46                 ` Charles Forsyth
2005-05-09  7:41           ` David Tolpin
2005-05-08 21:12       ` Charles Forsyth [this message]
2005-05-09 13:29         ` Nigel Roles
2005-05-09 14:03           ` Charles Forsyth
2005-05-10 17:09         ` boyd, rounin
2005-05-10 17:15           ` jmk
2005-05-10 18:34             ` boyd, rounin
2005-05-10 18:39               ` rog
2005-05-10 19:27               ` Ronald G. Minnich
2005-05-10 21:02                 ` David Leimbach
2005-05-10 21:20                   ` Bruce Ellis

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=8dc25d6e6eb4100818b09a511477f06e@terzarima.net \
    --to=forsyth@terzarima.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).