Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: Forth's list : the multo.
Date: Tue, 30 May 2017 21:30:25 -0700
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <87r2z5odge.fsf@nightsong.com>
References: <ogjdkj$c91$1@cherry.spenarnc.xs4all.nl> <6aab14e2-c89d-4be1-8ed3-f8461297b7b7@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="e17251fe7918e3c95bfc39c2c04dc3df"; logging-data="28912"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+qipftIN4AuMuUnqlzcxRT"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:kJA/JWEhbUfWIb65EZQ8k8F65BA= sha1:+7Pyntc4YdwiOu7fazBH+pyFcng=
Xref: csiph.com comp.lang.forth:60088

lehs <skydda.barnen@gmail.com> writes:
> It would be a nice challenge to get a concrete example of a higher
> level application that can't be managed in Forth.

I'd expect it can all be done in Forth, but you have to carefully manage
all of the scaffolding, probably including some kind of OOP system to
hold compound values; some kind of iteration convention for lists,
arrays, or what have you; and ways to pass those things to HOF's, along
with XT's all over the place.  It's a lot of complexity to follow and
likely to be bug-prone.  It's not impossible.  It's just harder than it
would be if those features were built in.