Jeff King <peff@xxxxxxxx> writes: >> Looks like /usr/ucb/tr is OK with this, but /usr/bin/tr is not. Both >> seem to handle the more verbose: >> >> tr \ >> 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ' \ >> 'nopqrstuvwxyzabcdefghijklmNOPQRSTUVWXYZABCDEFGHIJKLM' Besides tests, I think we have invocations of "tr" that Solaris people might want to audit in the real scripts. POSIX does not require [] around the strings, but when from-string and to-string are of the same length, having [] around them would not hurt (they transliterate to themselves) and that is the only reason why we tend to use [] form to help potential porters to ancient System V systems ;-) filter-branch uses A-Z (BSD style) range which also is Kosher in POSIX but will break historical System V that requires [] around ranges. bisect has "tr '[\012]' ' '" which I think we can get rid of by rewriting the users of the resulting string. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
