address RedHat BZ#496791: fix currently not possible, because the code

which escapes $(…) content does not know if an imbedded ‘#’ is a comment
leader or something else like “16#foo”, “${#bla[*]}”, “${foo#bar}”, &c.
and the comment skip code does not know about nesting beforehand
⇒ document this problem in the place where it already documents that
  the current code does not properly handle nested $($(…)) expressions

patches welcome

mksh.1

@@ -1,4 +1,4 @@
-.\" $MirOS: src/bin/mksh/mksh.1,v 1.157 2009/04/07 21:23:28 tg Exp $
+.\" $MirOS: src/bin/mksh/mksh.1,v 1.158 2009/04/22 16:25:12 tg Exp $
 .\" $OpenBSD: ksh.1,v 1.128 2009/03/06 12:28:36 jmc Exp $
 .\"-
 .\" Try to make GNU groff and AT&T nroff more compatible
@@ -30,7 +30,7 @@
 .el .xD \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8
 ..
 .\"-
-.Dd $Mdocdate: April 7 2009 $
+.Dd $Mdocdate: April 22 2009 $
 .Dt MKSH 1
 .Os MirBSD
 .Sh NAME
@@ -1029,7 +1029,8 @@ but it is carried out more efficiently because no process is started.
 .Sy Note :
 .Pf $( Ns Ar command Ns \&)
 expressions are currently parsed by finding matching parentheses,
-regardless of quoting.
+regardless of quoting; comments containing quote characters are
+not handled correctly.
 This should be fixed soon.
 .Pp
 Arithmetic substitutions are replaced by the value of the specified expression.