Linda W <[EMAIL PROTECTED]> writes: > I believe bash is broken in regards to using "any" number after > "\" as an octal value. The shell specifications require the leading > zero for an octal constant
I'm afraid this is backwards. This POSIX+XSI requirement constrains applications, not implementations. POSIX requires that if an application wants an octal escape for (say) the character with octal code 123, it must execute "echo '\0123'". If an application executes "echo '\123'" (without the "0"), POSIX says that the results are implementation-defined. Hence Bash can interpret \123 as an octal escape as well, if it so chooses, and still conform to POSIX+XSI. A similar analysis applies to \x escapes. For details, please see <http://www.opengroup.org/susv3xcu/echo.html>. Autoconf deals with shells that do not conform to XSI, and where the results are implementation-defined if there's a backslash anywhere in the string, so to some extent this point is moot for Autoconf (though it's undeniably a portability problem, one that is documented in the Autoconf manual under "Limitations of Builtins"). _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
