Re: [PATCH 8/8] one ugly test to verify basic functionality
- From
Elia Pinto <gitter.spiros@gmail.com>
- Date
- Feb 5, 2016, 13:38 UTC
- Message-ID
- <CA+EOSBn_HB8LABaN497zkr6tvCdqoQXhK=ecsLMx2c5CaJRg1A@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.2.20.1602051417490.2964@virtualbox>
2016-02-05 14:20 GMT+01:00 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
Show 16 quoted lines
> Hi Elia, > > On Fri, 5 Feb 2016, Elia Pinto wrote: > >> From the git coding guideline : "We prefer $( ... ) for command >> substitution; unlike ``, it properly nests. It should have been the way >> Bourne spelled it from day one, but unfortunately isn't." > > There was only one time in my life as a developer when I had to change a > $(...) to a `...` construct. I do not really remember all the details, but > I think it was on MacOSX, and it was inside a case ... esac and the > closing parentheses was mistaken for a case arm (the $(...) construct > might have been multi-line, is the only thing that would make sense in my > mind. > > Did you hear of similar problems?
I not personally. The autoconf manual does not seem to me (for that i can remember) to mention this possible incompatibility, for example.
Best
> > Ciao, > Dscho