Some variables, that were unquoted intentionally were converted to arrays.
According to ShellCheck's documentation:
Quoting variables prevents word splitting and glob expansion, and prevents
the script from breaking when input contains spaces, line feeds, glob
characters and such.
Related: https://www.shellcheck.net/wiki/SC2086
Related: #470
According to ShellCheck's documentation:
Use "$@" (with quotes) to prevent whitespace problems. $* and ${array[*]},
unquoted, is subject to word splitting and globbing.
Related: https://www.shellcheck.net/wiki/SC2048
Related: #470
According to ShellCheck's documentation:
-a and -o in [ .. ] test expressions are not well defined, and can cause
incorrect results when arguments start with dashes or contain !.
Related: https://www.shellcheck.net/wiki/SC2166
Related: #470
According to ShellCheck's documentation:
Double quotes around $@ and ${array[@]}) prevent globbing and word splitting
of individual elements, while still expanding to multiple separate arguments.
Related: https://www.shellcheck.net/wiki/SC2068
Related: #470
Change license of envml and envml.cmd scripts from GPLv3+ to GPLv2+.
Align this way all files from the Modules project under the GPLv2+
license.
Consent has been obtained from the copyright holders (I and @jraphanel)
to perform such move. Consent from Jacques Raphanel was collected by
email.
Related to #389
Provide a dedicated batch file to provide similar behavior of envml bash
script but for CMD Windows shell. Update existing envml bash script to
provide same behavior for cmd and sh file (split argument over ';'
character, in addition to '&' character).
