coproc or whatever in bash and ksh (Was: Different variable assignments)

In article <vf0a1h$3sn0s$1@dont-email.me>,
Janis Papanagnou  <janis_papanagnou+ng@hotmail.com> wrote:

On 19.10.2024 13:45, Kenny McCormack wrote:

In article <vec3qb$3q4ms$3@dont-email.me>,
Lawrence D'Oliveiro  <ldo@nz.invalid> wrote:

On Fri, 11 Oct 2024 22:50:10 +0200, Frank Winkler wrote:
>

... but it still doesn't solve the issue that I need the result to be
visible in the parent shell.

>
   coproc { uname -sr; }
   read -u ${COPROC[0]} var3
   wait $COPROC_PID
   echo $var3

 
I'm actually a fan of "coproc" in bash, and I use it in my scripting, but I
think it is overkill in most cases.  [...]

>
Also, if above code is how to use co-processes in Bash, I consider
that extremely clumsy (if compared to, say, Ksh).
>
(Mileages may vary, of course.)

I think he was being intentionally verbose for pedagogic purposes.

I won't bore you with the details, but obviously a lot of the text in the
quoted 4 lines is unnecessary in practice.

Just out of curiosity, how would you (Janis) do this in ksh?

--
The randomly chosen signature file that would have appeared here is more than 4
lines long.  As such, it violates one or more Usenet RFCs.  In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/ForFoxViewers