Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #43680 > unrolled thread

Re: Forth at GitHub

Back to article view | Back to comp.lang.forth

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Forth at GitHub Chris Curl <ccurl609@gmail.com> - 2015-11-23 12:20 -0800
    Re: Forth at GitHub Lars Brinkhoff <lars.spam@nocrew.org> - 2015-11-23 21:48 +0100
    Re: Forth at GitHub Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-24 12:16 +0000
      Re: Forth at GitHub Unknown <dog@gmail.com> - 2015-11-26 00:23 +0000

#43680 — Re: Forth at GitHub

On Friday, February 13, 2015 at 2:32:07 AM UTC-5, Lars Brinkhoff wrote:
> Hello,
> 
> I have tried to locate all GitHub repositories written in Forth.
> The result is this list of starred repos:
> 
> http://github.com/stars/ForthStar
> 
> Additions or corrections are welcome.  I currently include only
> software that has a substantial amount of Forth code, i.e. not
> zillions of toy Forths written in JavaScript.
> 
> Regards,
> Lars Brinkhoff

I have a new one ... 

https://github.com/CCurl/Forth-PCode-Asm

[toc] | [next] | [standalone]

#43683

Chris Curl wrote:
> Lars Brinkhoff wrote:
>> I currently include only software that has a substantial amount of
>> Forth code
>
> I have a new one ... 
> https://github.com/CCurl/Forth-PCode-Asm

Rewrite the PCode interpreter in Forth, and you're in!

[toc] | [prev] | [next] | [standalone]

#43703

Chris Curl <ccurl609@gmail.com> writes:

>On Friday, February 13, 2015 at 2:32:07 AM UTC-5, Lars Brinkhoff wrote:
>> Hello,
>>
>> I have tried to locate all GitHub repositories written in Forth.
>> The result is this list of starred repos:
>>
>> http://github.com/stars/ForthStar
>>
>> Additions or corrections are welcome.  I currently include only
>> software that has a substantial amount of Forth code, i.e. not
>> zillions of toy Forths written in JavaScript.
>>
>> Regards,
>> Lars Brinkhoff

>I have a new one ...

>https://github.com/CCurl/Forth-PCode-Asm

Also https://bitbucket.org/avanderhorst/yourforth

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.)















A















(It is not finished
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

[toc] | [prev] | [next] | [standalone]

#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.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.forth

csiph-web