FPForth

(a) Use it from a terminal window @19,200 baud. Ariba is just testing a new PropTerminal for it
(b) Details see below; some "FORTH for Dummies" will follow
(c) There are obviously some problems with the early versions... I try to keep you up to date so you need not wonder

Status FPForth 0.72
- stack underflow issue has been fixed
- auto Hydra recognition, so there is no extra binary for the hydra any longer!
- Frohf has prepared a short but comprehensiv PDF with a list of all implemented WORDs

Issues

- ." does not work correctly

Some WORDs explained - (0.71):

WORD ( Stack before -- Stack after ; <string> ) C/I/COG

C = Compile only
I = Immediate
COG = executed inside the COG without any internal reference to the HUB

"Stack Notation" as standard with FORTH, using the following data descriptors:

Comments

Would it be possible to add a "bignum" function to FPForth... I would like to do completely unscaled integer math on the Prop. For example... adding two integers the size of the Encyclopedia Britanica together.

It has been years since I have done anything in Forth so I have some relearning to do. Someone else might have some better recommendations but I am starting by reading two·of Leo Brodie's books·that are available on the Internet

Any chance that this propeller forth will support CREATE ... DOES> ? Last that I looked on the German forum I didn't see DOES> present. I don't know if it's missing due to technical difficulty, ideology (e.g. Ting's eForth), or maybe I just missed it.

I think what LewisD meant was that without the source code, this could become another abandonded project like Cliff's Forth. It sounds like frohf will be publishing source as soon as the first full release is ready. As I understand it, this will include SD/EEPROM file support and the ability to access spin/asm objects running on other cogs.

Personally I am waiting for Propeller Terminal support via PC_Interface and the ability to call my own Bioloid communication driver code. In the mean time, I am re-learning Forth and working on my driver and sensor code.

By the way, What was changed in version 0.70 other than the·crystal speed?

Don't fear!
Of course this can always happen with any one-man-project...
But we think it has first to get some internal stabiliity before it should be allowed to "spawn" into variants...

The community is small.. In fact I have no idea how large at all!? This forum has 10,000 users, so 20k to 30 k may be a good guess - but may be not...

<Edit> My mistake!! 10 k is the count for ALL Parallax forums, impossible to separate them. So according to popularity, history, and the "feeling" from the Propeller forum, I should say there are 1k interested in propeller rather than 10k ... So there is no justification for jumping to 20k to 30k as I did the other day... </Edit>

I should say - and this is again a guess, not even an "educated" one:

75% SPIN only

10% SPIN with mixture of assembly language

10% with high interest in C-Compiler, now messing arround with SPIN and assembly

4% interested in an alternative high performance development system for dedicated and customized Propeller solutions; FORTH being their favourit, but willing to change to C when it's good, or stay with assembly if FORTH does not perform...

1% FORTH addicts

Well 1% is around 200.. not so bad
<Edit> But after a reconsideration by far less :-( </Edit>

This Forth uses the serial connection to the PC for its console. You need to run a program like Hyperterminal on the PC with a connection at 19.2KBaud. There's no support currently for VGA or TV and the PS/2 keyboard.

New version 0.71 (see first posting)
- also displays number of used stack elements
- DIRA, INA , OUTA now work!
- new words:
CHAR
[noparse][[/noparse]CHAR]
COG@ -- to be used with Propeller constants, see below
COG!
DOES>
I+
I-
I
WAITTICKS

Is the ! and @ documentation correct? At first it says that "w" is 32-bit, then later it says that ! and @ store/load 16-bit values, but uses "w" in the stack comment.

Also I think that the "COG" implies no HUB access, but aren't these accessing RAM through the hub? Maybe it really means that the word exists solely in the COG, but it can still take actions that require the use of the hub?

Also DOES> didn't make it into the list at the top. Glad to see that it was added to the forth though.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔Nothing is impossible, there are only different degrees of difficulty.

Sapieha

RegardsSapieha
_____________________________________________________Nothing is impossible, there are only different degrees of difficulty.For every stupid question there is at least one intelligent answer.Don't guess - ask instead.If you don't ask you won't know.If your gonna construct something, make it as simple as possible yet as versatile/usable as possible.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔Nothing is impossible, there are only different degrees of difficulty.

Sapieha

RegardsSapieha
_____________________________________________________Nothing is impossible, there are only different degrees of difficulty.For every stupid question there is at least one intelligent answer.Don't guess - ask instead.If you don't ask you won't know.If your gonna construct something, make it as simple as possible yet as versatile/usable as possible.