> The divergence between pdksh and AT&T ksh has been rather an inconvenience
> to nearly everyone.  Ironically, I like pdksh better.

I think the convenience mostly results just from the choice to provide
pdksh as /bin/ksh.  That would be ok even if it were a true superset of
ksh, but as it's a superset-of-a-severe-subset it leads to the kind of
inconvenience where you have a perfectly good script written in valid
KornShell and it starts with #!/bin/ksh so there should be no mistake,
and on NetBSD it seems to run until the associative arrays or float
arithmetic or calendar computations or discipline functions break. And
then there are other things that break if you're used to pdksh and you
go to a system with ksh and expect it to be the same. There's nothing
wrong with pdksh as its own shell a little similar to ksh, and nothing
wrong with liking it better - it's really just the naming confusion that
causes headaches.

-Chap