zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: 4.0.1-pre-1
Date: Sun, 18 Feb 2001 01:43:17 +0000	[thread overview]
Message-ID: <1010218014317.ZM20759@candle.brasslantern.com> (raw)
In-Reply-To: <20010217005359.7B9C8139BA@pwstephenson.fsnet.co.uk>

On Feb 17, 12:53am, Peter Stephenson wrote:
} Subject: Re: 4.0.1-pre-1
}
} Ignoring most of the items which are associated with long discussions
} (pah!) or the ones which may not even be bugs (pah! pah!):

We should at least record somewhere (the BUGS file?) those that really
are bugs, so that we don't forget to address them later.

} > There's the ksh incompatibility with array export, 9576.
} 
} There's some commented-out code in there in one place already.  I think we
} should make ksharrays export the first word and with noksharrays, to be
} logical, export the array joined the same way we always get an array as a
} single word (c.f. singsub()).  We should make sure we don't export the
} array if it's tied to a colon-array.  I don't think we should export
} associative arrays at all --- the order is undefined, so we can't guarantee
} compatibility with ksh, nor promise a particular form for the non-ksh
} exported value.  Unless anyone has ideas.

The way ksh appears to treat an unsubscripted associative array reference
is to substitute the element whose hash key is "0".  That is, no matter
what kind of array it is, $array == $array[0].  The associative array
code in getstrvalue() already does this, but only when `emulate ksh' is
in effect (just ksharrays is not enough to activate it).

So one issue is whether `emulation == EMULATE_KSH' should be replaced by
`isset(KSHARRAYS)' in a number of places in params.c.

For noksharrays, I think we should just leave well enough alone and not
export the arrays at all.  The only reason to export one is because you
want to import it again, and tying to a colon-array is a more reliable
way of accomplishing that.  Of course there are joining/splitting issues
either way.

We could export an array as a whole bunch of variables ARRAY[0]=... etc.,
but then some programs (older shells in particular) get all huffy because
the string to the left of the `=' is "not an identifier".

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-02-18  1:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 12:35 4.0.1-pre-1 Peter Stephenson
2001-02-14 12:55 ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-14 17:32 ` 4.0.1-pre-1 Bart Schaefer
2001-02-14 17:50   ` PATCH: 4.0.1-pre-1 Peter Stephenson
2001-02-17  0:53   ` 4.0.1-pre-1 Peter Stephenson
2001-02-18  1:43     ` Bart Schaefer [this message]
2001-02-19  6:15       ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-19 22:00         ` exported functions (was Re: 4.0.1-pre-1) Oliver Kiddle
2001-03-06  7:57   ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-15 14:21 ` `make check' error [ Re: 4.0.1-pre-1 ] Fletch
2001-03-06  8:44 ` 4.0.1-pre-1 Alexandre Duret-Lutz
2001-03-06 10:31   ` 4.0.1-pre-1 Peter Stephenson
2001-03-06 14:24     ` 4.0.1-pre-1 Alexandre Duret-Lutz
2001-02-14 13:43 4.0.1-pre-1 Sven Wischnowsky
2001-02-15  6:30 ` 4.0.1-pre-1 Andrej Borsenkow
2001-02-16 14:56 4.0.1-pre-1 Sven Wischnowsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1010218014317.ZM20759@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).