Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Unknown <dog@gmail.com>
Newsgroups: comp.lang.forth
Subject: Re: Forth at GitHub
Date: Thu, 26 Nov 2015 00:23:48 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 88
Message-ID: <pan.2015.11.26.00.24.54@gmail.com>
References: <854mqq6zd6.fsf@junk.nocrew.org> <dc3e3683-05ab-4630-93ce-0264004672a6@googlegroups.com> <5654550c$0$23755$e4fe514c@news.xs4all.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 26 Nov 2015 00:23:48 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="4beea46cef2d423456f56462f4713521"; logging-data="4543"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+dEpXoUalf3adl5WV3nyHKqPC0T1yxrKw="
User-Agent: Pan/0.133 (House of Butterflies)
Cancel-Lock: sha1:0h96x3YXV+HSLvra23ubHYRRSek=
Xref: csiph.com comp.lang.forth:43790

On Tue, 24 Nov 2015 12:16:12 +0000, Albert van der Horst wrote:

> Chris Curl <ccurl609@gmail.com> writes:
> 
--snip --
> 
>>I have a new one ...
> 
>>https://github.com/CCurl/Forth-PCode-Asm
> 
> Also https://bitbucket.org/avanderhorst/yourforth
> 
I'll fetch and read those.
> This is my attempt at improving jonesforth further by better motivation
> of changes, full docs and exercises.
> 
> Because jonesforth was loosely based on ciforth, 1] I could get very
> close to jonesforth with the benefits of comprehensive test and pdf
> doc's. My original documents explain some design decisions better than
> Jones did.
> 
> The exercises are interesting for those who want to understand design
> decisions, and/or write her own Forth.
> 
> Groetjes Albert
> 
> 1] Register allocation, threading model, BRANCH , naming for stack
> initialisation (DSP@ DSP! R0 etc.)
 
The 'mixing of interpreting & compiling' is confusing for me,
but colors work very well for me: to separate concerns.
So I'm keen to get rainbowforth running 'properly'.
[colorforth is tied to windows, so is no good for me.]

So far RF tests OK with eg:
 tst3 7 3 - . ;
 tst4 tst3 5 dup + . tst3 9 4 - . ; tst4
[RF replaces colon with <color of the defined word>]

I'm trying to debug <"begin" is unknown>
but the overall structure is confusing.
I don't understand how/what the harness is.
His docos read:-------
Compiler Harness.

 C code compiles by calling a few Forth words.
 These Forth words are defined using a small
       set of built-in words.
 Small table of C entry points allow Forth to
      access system resources.
-----------------------------
Harness Required Words.

 execute-forth
 literal
 compile,
 variable
-----------------------------
Harness Supplied Words.

 macro
 forth
 smudge
 unsmudge
 b,
 windows?
 load
 thru
 heap-dump
 word-dump
-------------------------------
Harness Supplied Entry Points.

 load
 print_number
 key
 emit
 library_load
 library_symbol
------------------
Can someone explain how this harness fits into the:
asm, C, forth, language heirarchy?

== TIA.