Hi,
On 25/08/17 03:41, Antonio Quartulli wrote:
On 25/08/17 04:21, David Sommerseth wrote:
On 24/08/17 21:18, Gert Doering wrote:
(gen-release-tarballs.sh only needs to work on FreeBSD and Linux, and
FreeBSD's /bin/sh is sufficiently modern so so it's likely to work
- but the test scripts need to run robustly everywhere a user builds,
so never assume "because bash says so!" is a way anywhere but into worlds
of pain. And yes, we've been there before :-) )
And to avoid style confusions ... as long as we can avoid having "one
style" on the test scripts and "another style" on the dev-tools scripts,
that will be easier to review and maintain.
We can have more slack in dev-tools, but if we deviate, then we need to
properly document it so we won't forget why.
I also think it is a bad idea to have different styles. If we have to
agree on something, it should be valid for every file of that type.
Let's postpone this for when we'll have tested various platforms.
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 ;)
JM2CW,
JJK
------------------------------------------------------------------------------
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
