From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: A.Main@dcs.warwick.ac.uk (Zefram)
Cc: A.Main@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu
Subject: Re: (NULL == 0) ?
Date: Tue, 28 May 1996 00:00:42 +0200 (MET DST) [thread overview]
Message-ID: <199605272200.AAA02444@hzoli.ppp.cs.elte.hu> (raw)
In-Reply-To: <20765.199605271307@stone.dcs.warwick.ac.uk> from Zefram at "May 27, 96 02:07:05 pm"
> >A couple of other questions about Unix and C standards: does anything
> >guarantee that a variable is always 8 * sizeof(var) bits long?
>
> Only if a byte is 8 bits long and there are no holes in the integral
> types. This type of holes are very rare, and we assume 8 bit bytes
> elsewhere. I don't think we actually assume this directly anyway.
It is used to determine the size of buffers to store the string
representation of an integer. Just grep for 'SIZEOF_LONG \* 8'.
> > Does any Unix or C standard guarantees that an int always has at
> >least 32 bits?
>
> No. But C guarantees that long is at least 32 bits, so if there's
> anywhere we need 32 bits we should change it to use long. I don't know
> of anywhere in zsh tht needs fixing in this respect.
ntype in struct node has to be at least 32 bit long but it is defined to
int. But it would be wasting of memory to use long on systems where int
has 32 bits and long has 64.
In hashtable.h it is assumed that sizeof(void*) >= sizeof(long).
Zoltan
next prev parent reply other threads:[~1996-05-27 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-25 14:38 clwords bugfix Zefram
1996-05-25 18:02 ` Richard Coleman
1996-05-25 20:52 ` Zefram
1996-05-25 21:25 ` (NULL == 0) ? Richard Coleman
1996-05-25 22:00 ` Zefram
1996-05-27 0:00 ` Zoltan Hidvegi
1996-05-27 6:39 ` Bart Schaefer
1996-05-27 7:29 ` anthony baxter
1996-05-27 13:07 ` Zefram
1996-05-27 22:00 ` Zoltan Hidvegi [this message]
1996-05-27 22:11 ` Zefram
1996-05-27 22:41 ` Zoltan Hidvegi
1996-05-27 22:54 ` Zefram
1996-05-28 4:54 ` Bart Schaefer
1996-05-27 23:36 ` Bart Schaefer
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=199605272200.AAA02444@hzoli.ppp.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).