Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [PATCH] using sysread/syswrite with coprocess

X-seq: zsh-workers 52920
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Anthony Heading <ajrh@xxxxxxxx>
Cc: zsh-workers@xxxxxxx
Subject: Re: [PATCH] using sysread/syswrite with coprocess
Date: Thu, 9 May 2024 15:38:43 -0700
Archived-at: <https://zsh.org/workers/52920>
In-reply-to: <fbda2f2c-ba0c-4d32-ae24-be3b3721091a@app.fastmail.com>
List-id: <zsh-workers.zsh.org>
References: <fbda2f2c-ba0c-4d32-ae24-be3b3721091a@app.fastmail.com>

On Thu, May 9, 2024 at 6:09 AM Anthony Heading <ajrh@xxxxxxxx> wrote:
>
> Does the patch below make sense?  I couldn't see a way to do this otherwise

There's nothing technically wrong with the patch, but you can do
  coproc ...
  exec {coprocin}>&p
  exec {coprocout}<&p
and then
  syswrite -o $coprocin ...
or
  sysread -i $coprocout ...

Whether it makes sense to support direct access to the coproc FD by
either "-o p" / "-i p" or simply -p as with print / read, or neither,
I will leave for larger discussion.

References:
- [PATCH] using sysread/syswrite with coprocess
  - From: Anthony Heading

Messages sorted by: Reverse Date, Date, Thread, Author