My OS is Linux (kernel 4.08.something) and AIX (7100-04-01-1543), the used ksh versions are:
ksh88: Version M-11/16/88f (AIX)
ksh93: Version M 93t+ 2009-05-01 (AIX), Version M 93u (Linux)
When writing a parser for stanza files in ksh i encountered a rather strange behavior. Here is a stripped down version of the parsing loop (i left out the actual parsing for clarity if anyone is interested i can post it), i marked the two critical lines in bold:
Code:
#! /bin/ksh
typeset chLine=""
typeset chChar=""
while read chLine ; do
print - "-- Begin Line: $chLine"
while [ -n "$chLine" ] ; do
chChar="${chLine%${chLine#?}}"chLine="${chLine#?}"
print - "\n Line: \"$chLine\""
print - " Char: \"$chChar\""
done
done < /iput/file
exit 0
Here is the output of this with the sample file (1 line) containing item=value, which works as expected:
Now, because i wanted to have comments in my stanza files (which the parser should filter out), but needed to make escaped comment chars possible i tried with the line item=val\\#ue. Here is the output running above script with with ksh88, which is as expected:
You are hoping the backslash in the expansion of ${chLine#?} will be treated as a literal backslash character. And, in the expansion of ${chLine} it is. But, in word in ${chLine%word} the backslash is an escape character. Since \# is treated as an escaped # in the pattern instead of the two character literal \#, there is no match and the string isn't removed from the expansion with the removal of a matching smallest suffix pattern.
This is one of the changes that was made to ksh88 behavior (that is handled differently in ksh93) while the POSIX shell standard was being developed.
I think this explains the difference you're seeing, but unless your script tests which version of ksh you're using and uses different code for the two cases, you may have trouble finding a common variable expansion that will get you what you want in both versions of the shell. Unfortunately, you can't use ${chLine:2} in ksh88 (but it gives you what you want in ksh93).
This User Gave Thanks to Don Cragun For This Post:
You are hoping the backslash in the expansion of ${chLine#?} will be treated as a literal backslash character. And, in the expansion of ${chLine} it is. But, in word in ${chLine%word} the backslash is an escape character.
After this i finally understood what the problem was in first place. Thank you for enlightening me.
Quote:
Originally Posted by Don Cragun
Maybe you'd like to try the following which should work with ksh88 and any POSIX conforming shell (including ksh93):
Thank you again for providing even a solution along with the explanation. I was already (reluctantly) dusting off my trusted old C compiler to write the parser there. I am indebted.
Hi Guys,
I wrote a collection of bash functions years ago and now need to use them again but
I'm getting some error messages when eval tries to expand the variables names.
I recollect that I used the shopt command to set one of the options but I can't quite
remember the command that I... (8 Replies)
Hi everyone !
Im trying to know from wich version of AIX KSH93 is available ?
Internet tell me 6.x and 7.x AIX are available, bue what about 5.x ?
Is KSH93 available on AIX 5.x ?
Is it the same way to manipulate variables as KSH93 on 7.x ?
Thanks for your support and have a nice day ! (2 Replies)
Hi Experts,
I have several shell scripts that have been developed on a Linux box for korn ksh93.
If we want to run this software on an AIX 6.1 box that runs ksh88 by default can we just change the she-bang line to reference /bin/ksh93 which ships with AIX as its "enhanced shell" to ensure... (6 Replies)
Hi Guys,
I have an issue with awk and variables. I have trawled the internet and forums but can't seem to get the exactt syntax I need.
I have tried using awk -v and all sorts of variations but I have hit a brick wall. I have spent a full day on this and am just going round in circles.
... (3 Replies)
Hi,
The following code finds the line containing fruits in test.txt and replaces instances of apple with banana.
ed -s test.txt <<< $'/fruits/s/apple/banana/g\nw'
What I want to do is put variables in the place of fruits, apple and banana.
I have tried replacing ' with " to get... (2 Replies)
Hi,
I have a script that calls an external program to perform some calculations and then I read with "grep" and "sed" values from the output files. I've noticed that performance of KSH93 degrades with every iteration. The output files are all the same size, so I don't understand why after the... (2 Replies)
Any means of running ksh93 in a ksh88-mode?
Might sound odd, but I want/need to restrict U/Win-developed scripts to correspond to the ksh88 version on my Solaris environment(s). Thanks. (2 Replies)
If have
var='$variable'
how can I expand $variable.
I have tried many thing like duble quotes/braces etc, but nothing worked.
I need the solution ASAP. (2 Replies)
07-03-2017
