[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: nofork command substitution
From: |
alex xmb ratchev |
Subject: |
Re: nofork command substitution |
Date: |
Fri, 19 May 2023 21:36:36 +0200 |
On Fri, May 19, 2023, 21:11 Greg Wooledge <greg@wooledge.org> wrote:
> On Fri, May 19, 2023 at 06:35:50PM +0200, alex xmb ratchev wrote:
> > so that i understand ,
> >
> > var=${ awk ... }
>
> There's no reason to use this new thing if you're calling awk, because
> awk is an external program. You might as well just use var=$( awk ... )
> instead.
>
> Either way, you're going to fork() and exec*() the external awk command.
>
o , this thing only useful for bash built ins ?
> ${| awk } no difference
>
> That one would give a different result because you're not assigning
> anything to REPLY. If I understand the new thing correctly.
>
and ' REPLY ' is default var for output or wha
btw thanks mate ..
greets
>
- Re: nofork command substitution, (continued)
- Re: nofork command substitution, Robert Elz, 2023/05/19
- Re: nofork command substitution, alex xmb ratchev, 2023/05/19
- Re: nofork command substitution, alex xmb ratchev, 2023/05/19
- Re: nofork command substitution, Chet Ramey, 2023/05/22
- Re: nofork command substitution, Martijn Dekker, 2023/05/22
Re: nofork command substitution, Chet Ramey, 2023/05/19
Re: nofork command substitution, alex xmb ratchev, 2023/05/19