Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: functions with redirections
- X-seq: zsh-workers 33290
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: PATCH: functions with redirections
- Date: Mon, 29 Sep 2014 18:02:57 -0700
- In-reply-to: <CAH+w=7ZzHKOQd8LCvdC+1gpCthb4Xd6t_8f9SjiXMssy=Vmn_g@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20140929205236.2eb5e622@pws-pc.ntlworld.com> <CAH+w=7ZzHKOQd8LCvdC+1gpCthb4Xd6t_8f9SjiXMssy=Vmn_g@mail.gmail.com>
On Sep 29, 1:53pm, Bart Schaefer wrote:
}
} foo() { echo foo; } >&3
} foo 3>&2
Tried this now; happily it works the same as bash.
} > If anyone wants something else to do they can think about whether I've
} > introduced any subtle memory leaks.
}
} I wouldn't expect any that would fool valgrind on a few simple examples.
I tried a function with an output descriptor redirection and an input
here-document and valgrind found no leaks.
Tangential remark: function-definition redirections to files may
produce unexpected errors when noclobber is set.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author