zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: The (e) glob flag and 'return'
Date: Thu, 11 Sep 2003 09:17:19 +0000	[thread overview]
Message-ID: <1030911091719.ZM8224@candle.brasslantern.com> (raw)

Consider this:

schaefer<503> print *.*(e['echo $REPLY'])
config.log
config.status
config.h
stamp-h.in
config.modules
config.cache
config.h.in
config.cache config.h config.h.in config.log config.modules config.status stamp-h.in
schaefer<504> 

This strikes me as odd:

schaefer<504> print *.*(e['echo $REPLY; return'])
config.log
config.cache config.h config.h.in config.log config.modules config.status stamp-h.in
schaefer<505> 

I would have expected that either the two were the same, or that the latter
would pass only config.log to "print".  How does "return" manage to cause
the subsequent evaluations to be no-ops but not errors?


                 reply	other threads:[~2003-09-11  9:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1030911091719.ZM8224@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.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).