From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>,
schaefer@nbn.com, Anthony Heading <aheading@jpmorgan.com>
Cc: zsh-workers@math.gatech.edu
Subject: Re: cshjunkieparen bothers me (and always has)
Date: Mon, 1 Jul 1996 18:03:20 -0700 [thread overview]
Message-ID: <960701180325.ZM1725@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: cshjunkieparen bothers me (and always has)" (Jul 1, 11:02pm)
In-Reply-To: Anthony Heading <aheading@jpmorgan.com> "Re: cshjunkieparen bothers me (and always has)" (Jul 1, 10:35pm)
On Jul 1, 11:02pm, Zoltan Hidvegi wrote:
} Subject: Re: cshjunkieparen bothers me (and always has)
}
} Below is the documentation. I do not know much about nroff so if something
} is wrong in it, tell me.
Looks OK to me.
On Jul 1, 10:35pm, Anthony Heading wrote:
} Subject: Re: cshjunkieparen bothers me (and always has)
}
} > ! Many of zsh's complex commands have alternate forms. These particular
} > versions of complex commands should be considered deprecated and may be
} > removed in the future. The versions in the previous section should be
} > preferred instead.
}
} If this syntax is being developed, it seems weird that it's deprecated.
The syntax isn't really being developed (except for my cshjunkietests
suggestion, which I put forth because I used to be a csh junkie). What
has happened is that a special case to *reject* an otherwise reasonable
syntax has been *removed*; this is deconstruction, not construction.
} Does anyone really want to get rid of it?
Just before 2.5.0 was released, there was a big push among some of the zsh
maintainers to remove csh-like features from zsh in favor of faithfully
emulating ksh. That faction no longer seems so vocal, probably because
zsh is now a more complete superset of ksh, so the fact that some extra
non-ksh syntax is available is less noticeable.
} If so, fine. But if the sentiment is that these forms should be
} available without setting options
That isn't quite an accurate depiction. These forms work for the same
reason that this kind of thing works:
if true ; ; ; then
echo bash or ksh would give a syntax error on ';'
fi
Zsh permits things like empty commands in a "list" syntax element and
other unambiguous combinations because it makes for a simpler parser.
It's actually more work in most cases to reject it than to accept it.
} shouldn't they:
} a) be supported;
} b) not be advised against in the manual?
I'd be all in favor of that.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
next prev parent reply other threads:[~1996-07-02 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-30 7:19 Bart Schaefer
1996-07-01 19:19 ` Bart Schaefer
1996-07-01 21:02 ` Zoltan Hidvegi
1996-07-01 21:35 ` Anthony Heading
1996-07-02 1:03 ` Bart Schaefer [this message]
1996-07-02 8:48 ` Peter Stephenson
1996-07-02 19:35 ` Bart Schaefer
1996-07-04 13:14 ` Zoltan Hidvegi
1996-07-04 15:58 ` 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=960701180325.ZM1725@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=aheading@jpmorgan.com \
--cc=hzoli@cs.elte.hu \
--cc=schaefer@nbn.com \
--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).