I found and fixed the problem. If you are building from the source, I can send you a fix.
On Sun, Dec 29, 2013 at 2:41 PM, Nathan Weeks <[email protected]> wrote: > Interval expressions don't seem to work in extended regular expressions > specified on the right-hand side of the "=~" operator in the latest ksh > alpha: > > ======================================== > $ echo ${.sh.version} > Version AIJM 93v- 2013-10-08 > $ str=AATAAT > $ [[ $str =~ (AAT){2} ]] && echo true > ksh: syntax error: `~(E)(AAT){2} ]] && echo true > ' unexpected > ======================================== > > For comparison, bash & zsh handle this ERE as expected: > ======================================== > $ echo ${BASH_VERSION} > 3.2.48(1)-release > $ str=AATAAT > $ [[ $str =~ (AAT){2} ]] && echo true > true > ======================================== > > ======================================== > % echo ${ZSH_VERSION} > 4.3.11 > % str=AATAAT > % [[ $str =~ (AAT){2} ]] && echo true > true > ======================================== > > Such interval expressions would need to be handled for "=~" for POSIX > conformance if the proposed "Extending Shell Conditionals" issue > (http://austingroupbugs.net/view.php?id=375) is accepted. > > -- > Nathan Weeks > IT Specialist > USDA-ARS Corn Insects and Crop Genetics Research Unit > http://weeks.public.iastate.edu/ > _______________________________________________ > ast-users mailing list > [email protected] > http://lists.research.att.com/mailman/listinfo/ast-users >
_______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
