From: Martijn Dekker <martijn@inlv.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] process substitution breaks when nested or traverses a function
Date: Tue, 24 Apr 2018 13:09:27 +0200 [thread overview]
Message-ID: <8d21cc5b-7e12-ff70-a9c1-1eb9973b492d@inlv.org> (raw)
In-Reply-To: <20180424114717.23a00f3c@camnpupstephen.cam.scsc.local>
Op 24-04-18 om 12:47 schreef Peter Stephenson:
> On Tue, 24 Apr 2018 10:30:16 +0000
> Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>> I don't know about "better", but I'd looked into this and wondered why
>> getproc() had two compile-time alternative implementations, one with
>> mkfifo() and one with /proc/self. Is this just about portability,
>> or...?
>
> Using a file descriptor is neater, because there's less cruft in the
> regular file system to clear up (and fewer associated security worries
> etc. etc.); however, /proc/self isn't guaranteed to be available on
> older systems, whereas FIFOs have been around for a good quarter
> century.
/proc/self (or /proc in general) is not available on some very much
current systems either, including at least macOS and OpenBSD.
/dev/fd is available on both of those, though.
- M.
next prev parent reply other threads:[~2018-04-24 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180421093602epcas1p4c7f4182661b42fa2e477f8fe61a3e132@epcas1p4.samsung.com>
2018-04-21 9:35 ` Francisco de Zuviría Allende
2018-04-24 9:43 ` Peter Stephenson
2018-04-24 10:30 ` Daniel Shahaf
2018-04-24 10:47 ` Peter Stephenson
2018-04-24 11:09 ` Martijn Dekker [this message]
2018-04-24 12:29 ` Peter Stephenson
2018-06-17 3:14 ` Francisco de Zuviría Allende
2018-06-18 9:28 ` Peter Stephenson
2018-06-27 9:04 ` Francisco de Zuviría Allende
2018-06-27 9:14 ` Francisco de Zuviría Allende
2018-06-27 9:18 ` Francisco de Zuviría Allende
2018-06-28 18:37 ` Daniel Tameling
2018-06-29 8:37 ` Peter Stephenson
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=8d21cc5b-7e12-ff70-a9c1-1eb9973b492d@inlv.org \
--to=martijn@inlv.org \
--cc=zsh-workers@zsh.org \
/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).