Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: Stoked
Date: Sun, 08 Nov 2015 14:09:37 -0800
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <87io5cta72.fsf@nightsong.com>
References: <d8be4416-4e14-49f8-b54f-54665bd7639a@googlegroups.com> <ba0d541b-dec8-466b-b5a2-9752323f574d@googlegroups.com> <n0qtc8$9ta$2@dont-email.me> <284a0c81-1d04-406d-a84b-39d4617375f3@googlegroups.com> <n0r3oc$5aa$1@dont-email.me> <n1ldkh$1nd$1@speranza.aioe.org> <n1lebj$efb$1@dont-email.me> <87egg1wu31.fsf@nightsong.com> <ZcidnVC92b6A3qPLnZ2dnUU7-KWdnZ2d@supernews.com> <87a8qpwl3x.fsf@nightsong.com> <n1lqve$1fh$1@dont-email.me> <87611dwio9.fsf@nightsong.com> <n1lvsi$mdb$1@dont-email.me> <871tc1wg1b.fsf@nightsong.com> <n1mp2q$luv$1@dont-email.me> <87pozluhfj.fsf@nightsong.com> <563f9314$0$23846$e4fe514c@news.xs4all.nl> <87vb9ctk8q.fsf@nightsong.com> <563f9862$0$23795$e4fe514c@news.xs4all.nl> <87r3k0tj9k.fsf@nightsong.com> <563fbdc2$0$23776$e4fe514c@news.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="1a9f5856d25720e42c135b990c70bebb"; logging-data="3576"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18QOlRhCAOs7byPUTMfIvF5"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:8fbggQSj/gwMMWlNaFmR/Elwisc= sha1:l18hZF+HQ7t17hbywZYlA1/b/s4=
Xref: csiph.com comp.lang.forth:43388

Albert van der Horst <albert@spenarnc.xs4all.nl> writes:
>>The Greenarrays stuff is all written with blocks
> No, colorforth was written in assembler. .. I've disassembled colorforth

Oh ok, that's the PC-hosted compiler.  I meant the the actual GA144
rom code, which uses blocks.  Chuck did release the asm source code
for Colorforth by the way.

> It had the best forth editor for blocks you've ever seen.
> You're not my worst enemy, and even then I wouldn't wish you
> to type in the source for the next version into those blocks.

Polyforth used blocks--was that equally bad?  Of course you'd want a way
to upload and download the whole contents of the target storage.

I'm imagining something like 4e4th except for a chip with more memory
(ram and flash) than the MSP430G2553.  So instead of just having an
interactive interpreter, the whole system could be there as source code
and dev environment, and could rebuild itself.  The MSP430FR6989 has
128KB of FRAM which might be enough for this, and there's a very nice
Launchpad board built around it.