Hi,
On Tue, Aug 29, 2017 at 06:19:21PM +0200, Jan Just Keijser wrote:
> my biggest complaint about the so-called modern $() notation is that it
> clashes/confuses the heck out of me when using proper variable usage,
> e.g. I find
> output=`${SOME_COMMAND} ${SOME_ARGS}`
> much better readable than
> output=$(${SOME_COMMAND} ${SOME_ARGS})
>
> especially since you are allowed to **NEST** $() strings, IIRC. Things like
>
> output=$(${cmd} $(${cmd2}))
>
> work, and in my view, thank god that you cannot do that using backtics ;)
well, yes, what you say :-)
(but I thought this was just my old age showing... having learned shell
scripting on a SCO Unix box, with only a *true* bourne shell installed,
no korn shell, no bash...)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
