From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: coleman@math.gatech.edu (Richard Coleman)
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh and portability
Date: Tue, 28 May 1996 13:44:04 +0200 (MET DST) [thread overview]
Message-ID: <199605281144.NAA19014@turan.elte.hu> (raw)
In-Reply-To: <199605272316.TAA12028@redwood.skiles.gatech.edu> from Richard Coleman at "May 27, 96 07:16:33 pm"
> There been a lot of talk in the last couple of days about
> various assumptions that zsh makes (NULL has all zero bits,
> or char has 8 bits, etc..).
>
> My suggestion would be to not worry too much about such things unless
> they become a problem. I want zsh to be portable as well, but not at
> the expense of needlessly complicating the code for machines that zsh
> will probably not run on anyway.
>
> In any portable unix software, you must make assumptions that are not
> guaranteed by any standard (ANSI C, POSIX, whatever). I don't think
> anything is wrong with this (withing reason). If the code is kept
> clean and well documented, and someone REALLY wants to run zsh on an
> OS that goes against these assumptions, then they could can port it
> themselves without too much trouble.
>
> I think time could be better spent documenting the assumptions that
> are made, rather than adding more complexity in the name of
> portability.
>
> Remember. Keep things as simple as possible. I will of course,
> repeat this mantra on a regular basis.
I agree, but if a change is simple and trivial, and improves portability
than it would be usefull to add.
Also I think that in the near future there will be systems where
sizeof(long) > sizeof(void*). The other problems will probably not come up
on modern systems but this one has to be handled somehow. In other words
we need a portable method to initialise a union.
Zoltan
prev parent reply other threads:[~1996-05-28 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-27 23:16 Richard Coleman
1996-05-28 11:44 ` Zoltan Hidvegi [this message]
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=199605281144.NAA19014@turan.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=coleman@math.gatech.edu \
--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).