* Clark J. Wang <[email protected]> [2012-01-17 15:30]:
> I have 4 versions of ksh93 at hand and following are all the ${.sh.version}
> strings:
>
> Version M 1993-12-28 p
> Version M 93t 2008-11-04
> Version JM 93u 2011-02-08
> Version jM 93u 2011-02-08
>
> And I remember (not quite sure) I've ever seen one version like 93q+.
>
> For new ksh users like me it seems to be a bit difficult to understand what
> `JM' means and what's the difference between `JM' and `jM'. And I don't
> know which one of `JM' and `jM' is newer. To write a kshrc which can work
> for all ksh versions I have to check the ${.sh.version} string but the
> format is not consistent and it's not as easy to parse and compare. So is
> it possible to use a more readable version string? Or we can introduce a
> new var like Bash's ${BASH_VERSINFO[@]}?
You can evaluate ${.sh.version} in an arithmetic context and do easy
comparisons:
$ print $(( .sh.version ))
20100621
According to the changelog this feature was introduced on 2008/08/13.
--
Guido Berhoerster
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
