From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: The sh substitution problem.
Date: Mon, 10 Jun 2002 16:07:34 +0000 [thread overview]
Message-ID: <1020610160735.ZM8154@candle.brasslantern.com> (raw)
In-Reply-To: <24097.1023710714@csr.com>
On Jun 10, 1:05pm, Peter Stephenson wrote:
} Subject: The sh substitution problem.
}
} This is tricky and I have no idea of its detailed feasibility. If
} anyone wants to try they should. Otherwise just make comments.
I think the discussion Oliver and I had earlier this year, e.g.
http://www.zsh.org/mla/workers/2002/msg00512.html
regarding passing around Parameter structs instead of Value structs, is
the key to this problem as well. If the right-hand-side of the :+ (etc.)
were encoded as a parameter, it can carry around all the state necessary
to properly substitute it when the time comes. Passing it around as just
a string or array is not sufficient, no matter what you do WRT preserving
nulls etc.
You sort of hint at this when you say:
} [It might be possible to keep val and aval as a pair in a structure,
} a sort of pseudo-parameter, and only convert between scalar and array
} when really necessary with a `forcescalar' or `forcearray'
} function/macro.]
Of course this is a more significant rewrite than just "fixing" multsub(),
but last year I had several goes at multsub() without coming up with
anything usable.
--
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
prev parent reply other threads:[~2002-06-10 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 12:05 Peter Stephenson
2002-06-10 16:07 ` Bart Schaefer [this message]
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=1020610160735.ZM8154@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.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).