From: Richard Coleman <coleman@math.gatech.edu>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: ksh compatibility
Date: Thu, 12 Oct 1995 14:19:56 -0400 [thread overview]
Message-ID: <9510121819.AA03938@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Thu, 12 Oct 1995 13:07:41 BST." <199510121207.NAA13791@bolyai.cs.elte.hu>
> > According to the "Korn Shell Ref" card (updated for ksh93) from SSC
> >
> > [[ str == pat ]]
> >
> > is preferred and
> >
> > [[ str = pat ]]
> >
> > is "obsolete" (but still works of course).
> >
> > Can the == for [[ be added to zsh? We've got some code that
> > needs to work on both ksh and zsh so it would be nice...
>
> My ksh manual from Solaris 5.4 (Last change: 3 Aug 1993) does not mention
> this, but I tried the ksh here, and it accepted the == syntax. Here is a
> patch to zsh to do that. This makes [[ ... = ... ]] and [[ ... == ... ]]
> equivalent.
Notice that he said ksh93. I think Solaris uses ksh89.
Also, I will probably add this since I think == is a more logical way
of representing this. But I must stress something important:
The goal of zsh is not to be a ksh clone. The goal of zsh (as far as I'm
concerned) is to be a powerful superset of sh that is especially good at
interactive use. The ksh compatibility we have now is more a matter of
convenience than the result of explicitly trying to copy ksh. Maintaining
ksh compatibility for common commands is a good idea, but I see no compelling
reason to copy every last detail of ksh.
Richard Coleman
coleman@math.gatech.edu
next prev parent reply other threads:[~1995-10-12 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-12 5:42 [[ str == pat ]] ? Glenn Barry
1995-10-12 12:07 ` Zoltan Hidvegi
1995-10-12 18:19 ` Richard Coleman [this message]
1995-10-12 20:36 ` Glenn Barry
1995-10-13 4:32 ` Arnold D. Robbins
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=9510121819.AA03938@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=hzoli@cs.elte.hu \
--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).