AST Users, After upgrading ksh, the second backlash in “${myVar/\</\>}" is no longer considered as an "escape" character.
At my request, our Sys Admin upgraded ksh on one of our Linux servers. In the code example below, I escaped the "<“ and “>” characters, as I have in other code that has worked for years. Now, the output of the example statement includes an unexpected “\” character. Is the new behavior wrong? Or have I always been doing the wrong thing by escaping (in this example) the “>” character? If escaping special characters in the “change-to” part was incorrect, why has my other code that escapes special characters in the “change-to” part never before printed out those “\” characters? #================================ #-- Red Hat Enterprise Linux Server release 6.4 (Santiago) #-- ksh version sh (AT&T Research) 93u+ 2012-08-01 #— "rpm -qa" reports: ksh-20120801-21.el6_6.2.x86_64 #-- #— UPGRADED FROM: #— ksh version sh (AT&T Research) 93t+ 2010-06-21 #— "rpm -qa" reports: ksh-20100621-19.el6_4.4.x86_64 #— $ myVar=“x<y" $ print “${myVar/\</\>}" x\>y #— #— Previously, the printed value would have been: x>y #================================ Thanks, Dan Rickhoff _______________________________________________ ast-users mailing list ast-users@lists.research.att.com http://lists.research.att.com/mailman/listinfo/ast-users