contrary to what I said in revision 1.453 we evidently d̲o̲ export arrays…

(XXX there’s a comment in var.c:typeset() still to the contrary, with assumptions…)
This commit is contained in:
tg 2018-04-28 07:03:17 +00:00
parent e42dc7afcb
commit 1c24f0dbc7
1 changed files with 3 additions and 6 deletions

9
mksh.1
View File

@ -1,4 +1,4 @@
.\" $MirOS: src/bin/mksh/mksh.1,v 1.455 2018/04/27 17:20:39 tg Exp $ .\" $MirOS: src/bin/mksh/mksh.1,v 1.456 2018/04/28 07:03:17 tg Exp $
.\" $OpenBSD: ksh.1,v 1.160 2015/07/04 13:27:04 feinerer Exp $ .\" $OpenBSD: ksh.1,v 1.160 2015/07/04 13:27:04 feinerer Exp $
.\"- .\"-
.\" Copyright © 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, .\" Copyright © 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
@ -77,7 +77,7 @@
.\" with -mandoc, it might implement .Mx itself, but we want to .\" with -mandoc, it might implement .Mx itself, but we want to
.\" use our own definition. And .Dd must come *first*, always. .\" use our own definition. And .Dd must come *first*, always.
.\" .\"
.Dd $Mdocdate: April 27 2018 $ .Dd $Mdocdate: April 28 2018 $
.\" .\"
.\" Check which macro package we use, and do other -mdoc setup. .\" Check which macro package we use, and do other -mdoc setup.
.\" .\"
@ -4943,10 +4943,7 @@ See
above for the implications of this. above for the implications of this.
.It Fl x .It Fl x
Export attribute. Export attribute.
Parameters are placed in the environment of any executed commands; Parameters are placed in the environment of any executed commands.
this includes the array member with the key
.Dq 0
if the parameter is an array.
Functions cannot be exported for security reasons Functions cannot be exported for security reasons
.Pq Dq shellshock . .Pq Dq shellshock .
.It Fl Z Ns Op Ar n .It Fl Z Ns Op Ar n