Re: Re: Feature Requests - longer view

[email protected] wrote:
> If there's a structure so that the knowledge if various contributors
> can be accumulated, there will be progress.

There is such a structure.
Bookmark this: http://wiki.enst.fr/bin/view/Picforth/WebHome

(that site is down at the moment - not getting DNS reply - but it should 
hopefully be back up soon)

> So eg. someone(s) could list words to the glossary, and other(s) could
> fill in the 'answers'.   I.e. successive refinement. The task is never done,
> but can be useful from an early stage.

> PS. I'd like to revive my project which went dormant when:
> 1. DOSEMU wouldn't drive par-port for my programmer,

Consider switching to WINE - I use ICPROG under WINE for burning 
bootloader code into my PIC (after which I just use a linux bootloading 
client each time I compile a PicForth prog)

> 2. I didn't get satisfactory feed back of how to use arrays.

Creating an array:

    create arrayname $16 allot \ creates 16-byte read/write array

    arrayname 2 + @   \ fetches element 2

    $45 arrayname 2 + ! \ stores 0x45 into arrayname[2]

> Have we got a 'GROWING' examples-code-base ?
> Where I could see examples of array usage ?

If you only want read-only tables, in RAM, EEPROM or program flash, 
refer section 5.14 of the manual.

> 
> 
> 
> 
> _______________________________________________
> PicForth mailing list
> [email protected]
> http://lists.rfc1149.net/mailman/listinfo/picforth
> 
> 

-- 
Cheers
David