Bug fixes from pdksh-unstable-5.2.13.4, including "official" versions of

some that we had already fixed locally.
 o typeset -f FUNC doesn't print follows command (and expression) substitutions.
 o when re-allocating memory, too much may be copied from old memory.
 o set -o printed some options sans names.
 o emacs mode: <esc>. in very fist command causes core dump.
 o pdksh dumps core after a cd command.
 o typeset -i reports on array elements that have no value
   (at&t ksh reports on array base name - no index).
 o ulimit -ctn unlimittttted kills shell (resource exceeded).
 o ". /dev/null" says access denied.
 o flag field in aliases incorrectly changed (all flags set instead of
   clearing ISSET) in exec.c(flushcom).
 o ${#array[*]} prints largest index instead of number of (set) elements
   in an array (ksh88 does the former).
 o sys_siglist[] doesn't always have NSIG non-null entries...

1 files changed, 7 insertions, 3 deletions

diff --git a/bin/ksh/NOTES b/bin/ksh/NOTES
index 3979a77a7b4..906129eef42 100644
--- a/bin/ksh/NOTES
+++ b/bin/ksh/NOTES
@@ -1,4 +1,4 @@
-$OpenBSD: NOTES,v 1.4 1998/06/25 19:01:37 millert Exp $
+$OpenBSD: NOTES,v 1.5 1998/10/29 04:09:19 millert Exp $
 
 General features of at&t ksh88 that are not (yet) in pdksh:
     - exported aliases and functions (not in ksh93).
@@ -33,7 +33,7 @@ Known bugs (see also BUG-REPORTS and PROJECTS files):
 	  does not.  pdksh exits for neither.  Don't think POSIX requires
 	  an exit, but not sure.
 	- `echo foo | read bar; echo $bar' prints foo in at&t ksh, nothing
-	  in pdksh (ie, the read is done in a seperate process in pdksh).
+	  in pdksh (ie, the read is done in a separate process in pdksh).
     Misc:
 
 Known differences between pdksh & at&t ksh (that may change)
@@ -137,7 +137,7 @@ Known differences between pdksh & at&t ksh (that are not likely to change)
       and tracked aliases and normal aliases live in the same name space
       (eg, "alias" will list both tracked and normal aliases).
       in pdksh, -t does not imply -x (since -x doesn't do anything yet), and
-      tracked/normal aliases live in seperate name spaces.
+      tracked/normal aliases live in separate name spaces.
       in at&t ksh, alias accepts + options (eg, +x, +t) - pdksh does not.
       in pdksh, alias has a -d option to allow examination/changing of
       cached ~ entries, also unalias has -d and -t options (unalias -d
@@ -187,6 +187,10 @@ Known differences between pdksh & at&t ksh (that are not likely to change)
     - co-processes: if ksh93, the write portion of the co-process output is
       closed when the most recently started co-process exits. pdksh closes
       it when all the co-processes using it have exited.
+    - pdksh accepts empty command lists for while and for statements, while
+      at&t ksh (and sh) don't.  Eg., pdksh likes
+	while false ; do done
+      but ksh88 doesn't like it.
 
 Oddities in ksh (pd & at&t):
     - array references inside (())/$(()) are strange: