From: Jens Schweikhardt <schweikh@schweikhardt.net>
To: zsh-workers@sunsite.auc.dk
Subject: minor parsing bug in zsh 3.0.8
Date: Mon, 7 May 2001 16:02:52 +0200 [thread overview]
Message-ID: <20010507160252.A1540@schweikhardt.net> (raw)
hello, world\n
zsh won't parse function definitions with a space between the parentheses:
# foo ( ) { echo foo }
zsh: parse error near `}'
# foo () { echo foo }
# echo $ZSH_VERSION
3.0.8
The draft of the next POSIX spec makes ( and ) in function definitons
separate tokens,
function_definition : fname '(' ')' linebreak function_body
You might want to fix this for proper POSIX conformance. Thanks!
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
next reply other threads:[~2001-05-07 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 14:02 Jens Schweikhardt [this message]
2001-05-07 14:20 ` 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=20010507160252.A1540@schweikhardt.net \
--to=schweikh@schweikhardt.net \
--cc=zsh-workers@sunsite.auc.dk \
/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).