Sujet : Re: Why do we need "eval"? (Expect question)
De : gazelle (at) *nospam* shell.xmission.com (Kenny McCormack)
Groupes : comp.lang.tclDate : 13. Sep 2024, 12:21:07
Autres entêtes
Organisation : The official candy of the new Millennium
Message-ID : <vc1773$1u8fb$1@news.xmission.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
vc0f9n$ml8n$1@dont-email.me>, Rich <
rich@example.invalid> wrote:
Kenny McCormack <gazelle@shell.xmission.com> wrote:
ISTM that this {*} thing is a relatively recent addition to the langauge,
>
Not really, it was added in 8.5, which was released Feb 12, 2016 [1].
Although 2016 *is* relatively recent in regards to many expect scripts.
Well, yes, really, from the perspective of Expect.
That was my point - that Expect hasn't really changed much since the late
90s, and most of the active development was done then. The scripts that I
have in mind - such as "unbuffer" - date back to that era.
since Expect has been around for a long time, and most of the scripts that
do this sort of thing were written long ago.
>
Before 8.5, 'eval' was the way to perform the "splicing" that {*}
provides.
Right. OK.
I'm glad I learned about {*}.
-- This is the GOP's problem. When you're at the beginning of the yearand you've got nine Democrats running for the nomination, maybe one ortwo of them are Dennis Kucinich. When you have nine Republicans, sevenor eight of them are Michelle Bachmann.