From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: bash conversion trouble.
Date: Sat, 25 Feb 2017 21:05:08 -0800 [thread overview]
Message-ID: <34e05410-7940-aa48-2c35-1302b915f713@eastlink.ca> (raw)
In-Reply-To: <170225120927.ZM22787@torch.brasslantern.com>
On 25/02/17 12:09 PM, Bart Schaefer wrote:
> The point is that zsh "went" before there were arrays in bash to follow.
> "I'd have expected gorillas to be the same color as orangutans."
Yes, that much I know, if I stop to recall it.
> } One hears nothing but bad things about csh.
>
> Yes, the intent of zsh was to take only the good things from csh and for
> everything else be like the Bourne shell (which is NOT "like bash", nor
> is it even "like POSIX" which came even later).
Sure, but I've always presumed that bash is 'like' sh, for obvious
reasons so the likeness would come from the parent. Why was there zsh
and bash anyway? It seems to me that the goals would have been so
similar that two projects were a duplication of effort.
>
> In C it makes sense because arrays are based on pointer arithmetic so
> array[0] == *(array+0) == the start of the array. Shells don't have
> such pointer arithmetic, at least not exposed by default. That's even
> the reason that $0 == the program name, because in the underlying C
> the 0 element of the array passed to execve() is the program name.
>
Yeah, thanks for reminding me. zero base really is the more rigorously
correct.
next prev parent reply other threads:[~2017-02-26 5:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 1:35 Ray Andrews
2017-02-25 4:41 ` Bart Schaefer
2017-02-25 15:13 ` Ray Andrews
2017-02-25 15:26 ` Peter Stephenson
2017-02-25 15:55 ` Bart Schaefer
2017-02-25 16:24 ` Ray Andrews
2017-02-25 17:02 ` Bart Schaefer
2017-02-25 19:13 ` Ray Andrews
2017-02-25 20:09 ` Bart Schaefer
2017-02-26 5:05 ` Ray Andrews [this message]
2017-02-26 17:19 ` Bart Schaefer
2017-02-26 18:03 ` Ray Andrews
2017-02-26 21:10 ` Shell history (Re: bash conversion trouble.) Bart Schaefer
2017-02-26 23:23 ` Ray Andrews
2017-02-28 15:56 ` bash conversion trouble Stephane Chazelas
2017-02-28 19:27 ` Ray Andrews
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=34e05410-7940-aa48-2c35-1302b915f713@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).