zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Zefram <zefram@fysh.org>
Cc: Felix Rosencrantz <f_rosencrantz@yahoo.com>, zsh-workers@sunsite.dk
Subject: Re: Test failure in redirect.
Date: Tue, 5 Feb 2002 02:31:30 +0000	[thread overview]
Message-ID: <1020205023130.ZM28214@candle.brasslantern.com> (raw)
In-Reply-To: <20020204210337.GA4456@fysh.org>

On Feb 4,  9:03pm, Zefram wrote:
} Subject: Re: Test failure in redirect.
}
} Bart Schaefer wrote:
} >}   print foo >&-
} >} Error output:
} >} (eval):print:1: write error: bad file descriptor
} ...
} >+	/* Testing EBADF special-cases >&- redirections */
} >+	if ((fout != stdout) ? (fclose(fout) != 0) :
} >+	    (fflush(fout) != 0 && errno != EBADF)) {
} 
} I think the error message is correct and should remain; the test data
} is what needs to be fixed.

I don't think so ... closing stdout should not produce an error from a
builtin that does output.  E.g. here's bash:

[schaefer@zagzig schaefer]$ echo foo >&-
[schaefer@zagzig schaefer]$ echo $?
0
[schaefer@zagzig schaefer]$ 

The "print" command has to execute, e.g. in case it's given -P and there
are side-effects of the prompt expansion due to the PROMPT_SUBST option,
but it must not produce any output and it definitely shouldn't return 
nonzero.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2002-02-05  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31  6:41 Felix Rosencrantz
2002-02-04 18:45 ` Bart Schaefer
2002-02-04 21:03   ` Zefram
2002-02-05  2:31     ` Bart Schaefer [this message]
2002-02-05  2:46       ` Zefram
2002-02-05  5:22         ` 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=1020205023130.ZM28214@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=f_rosencrantz@yahoo.com \
    --cc=zefram@fysh.org \
    --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).