changeset 16836:308e8faf5e8a

init.sh: explain why $EXEEXT support uses aliases rather than functions * tests/init.sh: Add a comment.
author Jim Meyering <meyering@redhat.com>
date Tue, 08 May 2012 11:54:26 +0200
parents a80277ccfb15
children 579368b4bb16
files ChangeLog tests/init.sh
diffstat 2 files changed, 8 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2012-05-08  Jim Meyering  <meyering@redhat.com>
 
+	init.sh: explain why EXEEXT support uses aliases rather than functions
+	* tests/init.sh: Add a comment.
+
 	init.sh: don't let bash aliases interfere with tests
 	* tests/init.sh: Undefine any pre-defined aliases if the selected shell
 	is bash.  This avoids problems for those who alias standard commands to
--- a/tests/init.sh
+++ b/tests/init.sh
@@ -210,6 +210,11 @@
 # If this is bash, turn off all aliases.
 test -n "$BASH_VERSION" && unalias -a
 
+# Note that when supporting $EXEEXT (transparently mapping from PROG_NAME to
+# PROG_NAME.exe), we want to support hyphen-containing names like test-acos.
+# That is part of the shell-selection test above.  Why use aliases rather
+# than functions?  Because support for hyphen-containing aliases is more
+# widespread than that for hyphen-containing function names.
 test -n "$EXEEXT" && shopt -s expand_aliases
 
 # Enable glibc's malloc-perturbing option.