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:41:30 +0200 (MET DST) [thread overview]
Message-ID: <199605272241.AAA02676@bolyai.cs.elte.hu> (raw)
In-Reply-To: <25534.199605272211@stone.dcs.warwick.ac.uk> from Zefram at "May 27, 96 11:11:48 pm"
> >It is used to determine the size of buffers to store the string
> >representation of an integer. Just grep for 'SIZEOF_LONG \* 8'.
>
> If we change the `8' to `CHAR_BIT' (which will need to be determined at
> configuration time if there isn't a limits.h), it would be more
> portable. But we are assuming 8-bit bytes, as well as ASCII, in a lot
> of character handling code.
Bart wrote that ANSI C guarantees ASCII in the cases we need so that should
not cause any problems. I do not see where is is assumed that a char has 8
bits othar than buffer sizes. We do assume that char has at least 8 bits
but that's OK.
> >In hashtable.h it is assumed that sizeof(void*) >= sizeof(long).
>
> We should have a union there, as we do elsewhere. long and void * are
> sufficient, but it might be neater to have some other pointer types too
> (it would reduce casting, and would not decrease efficiency).
Here struct iparam is used for initialisation. It is used instead of
struct param since initialisation of a union might cause problems.
Zoltan
next prev parent reply other threads:[~1996-05-27 22:47 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
1996-05-27 22:11 ` Zefram
1996-05-27 22:41 ` Zoltan Hidvegi [this message]
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=199605272241.AAA02676@bolyai.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).