jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: Usage of $(...) instead of `...` in shell scripts
Date Thu, 09 Nov 2017 12:59:52 GMT


Am 6. November 2017 19:27:47 MEZ schrieb sebb <sebbaz@gmail.com>:
>On 6 November 2017 at 18:20, Felix Schumacher
><felix.schumacher@internetallee.de> wrote:
>>
>>
>> Am 6. November 2017 19:04:41 MEZ schrieb sebb <sebbaz@gmail.com>:
>>>The $() syntax is newer than the command files.
>>>i.e. it was not available when they were written.
>>
>> That's probably true. To be more specific: I would like to know,
>whether it is safe to change it.
>>
>> Do you know of any system, that has a default shell, that is not able
>to process $(..)?
>
>If there is any doubt, just leave it alone.
>
>It's not broken, so don't try to fix it ...

Well actually there is one bug still left that is related to quoting and spaces in variables
(path). 

It can be fixed with the old syntax, but I am still curious if there are any systems left,
that can work with the old expression, only. 

Regards, 
Felix 
>
>> Regards,
>> Felix
>>
>>>
>>>On 4 November 2017 at 22:58, Philippe Mouawad
>>><philippe.mouawad@gmail.com> wrote:
>>>> No idea why it’s like this
>>>>
>>>> On Saturday, November 4, 2017, Felix Schumacher <
>>>> felix.schumacher@internetallee.de> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> we have both forms of execution commands in our shell scripts.
>>>>>
>>>>> $(...) is the more modern form and should be preferred over `...`
>as
>>>>> explained on https://github.com/koalaman/shellcheck/wiki/SC2006
>>>>>
>>>>> Does anyone know, if there is a reason for using the old form
>`...`
>>>in
>>>>> our scripts?
>>>>>
>>>>> Regards,
>>>>>  Felix
>>>>>
>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.

Mime
View raw message