User:Helmar
From RevaWiki
Hi, nice to see you here :)
Im the developer of HelFORTH http://maschenwerk.de/HelFORTH . It's similar to Reva and has the same inspiration roots in Retroforth.
HelFORTH has a little different design to Reva. Eg. it uses just in time compilation at startup of a turnkey application instead of using a precompiled image. To make this process fast, HelFORTH preprocesses the sources for turnkeys to bytecode that helps with two things: first it makes the binaries small and secondly it acts as a cache for the dictionary - so the walks thrue the dictionary are minimized while startup.
For some comparisation of HelFORTH to Reva see Comparison_of_Reva/RetroForth/HelFORTH.
Some points on FORTH
- First, FORTH is no complete programming language for programming in FORTH.
- Second, FORTH is the most complete language you need to do programming.
You'll never ever "program in FORTH" - at least if you want to make a serious program. You'll always program in your own idiolect if you do something people would call to "program in FORTH".
This is one of the biggest advantages and also one of the biggest drawbacks of FORTH.
FORTH is no replacement for say C(++). FORTH is no replacement for Perl. It's no replacement for ...what you want...
FORTH is a tool to do the work as you think about the work. You can define your own language to solve the problems. In best case you need to describe the problems in FORTH only. At least what you produce is a description for the one that understands your idiolect.
Everything you need to describe the problem should be a "tool".
Some contributions to Reva
- "invented" the concept of the word classes (can I say so?)
- Yes, you can say so :) ron 07:45, 19 March 2006 (PST)
- the x86 disassembler
- tester since first hour :)

