Re: [Help-bash] which paradigms does bash support

[Tadeus Prastowo]

On Tue, Mar 13, 2018 at 4:52 PM, Garreau, Alexandre
<address@hidden> wrote:

[...]

> I’m currently trying to learn how to take advantage of streams (not
> normal pipes or std(in|out|err) but arbitrary user-defined ones (>&3 and
> 3<&1 for instance), named/bash-defined ones (necessarily in the other
> order it seems, there: {var}<&1 then >&${var}), process substitution
> (<(cmd) and >(cmd), sadly lacking a <>(cmd), or I maybe misunderstood
> the previous ones), and named pipes) to achieve that form of
> arborescence while saving file descriptors (and avoiding opening and
> closing a file again and again) and potentially making some
> parallelization, but using a lot of streams (as seeable by my preceding
> mail on this list) seems to introduce less readability and really little
> way of doing arborescent work (I initially hoped for something near
> “tee” but more complex, without intermediary files, and builtin).
>
> But then I wonder, command subtitutions execute sequentially (one arg
> evaluated at a time) instead of parallely as pipes, but it seems they do
> even when suffixing them with “&” anyway… is there any way of
> reproducing this arborescent lispy style of programming while keeping
> this form of parallelization bash usually simplify by putting forks all
> the way?

Perhaps this post would give you a partial answer:
https://unix.stackexchange.com/a/86372

--
Best regards,
Tadeus