When I have the construct, in 4.1:
1 #!/bin/bash
2
30
31 # trace control for subs
32 declare -ix Allow_Trace=$(((
33 _D_LowLevel |
34 _D_Provides |
35 _D_
36 )))
37
38 declare -ix Trace_off
Chet Ramey wrote:
The remaining consideration is whether or not there's a significant
body of scripts out there that rely on the current behavior. If there
isn't, I would strongly consider the change to require a leading `0'
in octal constants. I don't think that \x introducing hex constants
is
Henrik Nordstrom wrote:
Note: As far as I can tell the echo tests in the configure script
generated by autoconf-2.59 tests for quite many things but not \digit as
far as I can tell. I have not yet looked into the CVS version.
Regards
Henrik
---
Sorry, haven't been involved too much on t
Henrik Nordstrom wrote:
fre 2006-03-17 klockan 19:31 -0800 skrev Linda W:
Mystery solved.
My shell _expanded_ control sequences by default in echo. (echo "\1" -> becomes
"echo ^A").
Apparently there are literals in the configure script like "\\1" "\\2&q
Henrik Nordstrom wrote:
lör 2006-03-18 klockan 14:15 -0800 skrev Linda W:
Bash added the "feature" to allow dropping of the leading
"0", accepting strings: "\0nnn", "\nnn", and "\xHH". I'm guessing that
most bash users run in a
