[PicForth] Re: Feature Requests - longer view

[easlab at absamail.co.za]

> Alex> 2. It would be extremely helpful for beginners if the
> Alex> documentation included a glossary of every picforth word with a
> Alex> brief description of what it does.
> 
> Be my guest :-) I can help, but I don't have the resources to do
> that.

William Kitchen wrote:-
> I'd settle for just a simple list without any explanatory text. Perhaps 
> that could be automated? There's plenty of sources of info for anything 
> that corresponds to conventional Forth words. But the usefulness of that 
> is limited by not easily knowing what's implemented.

Samuel Tardieu wrote:-
> I'm not convinced that this would be that useful. If you need a word,
> you can test in a few seconds whether it is implemented or not, and
> implement it (and share it ideally) in a few minutes.

PicForthList is surging ahead nicely now, having reached a critical mass.
This was made possible by the foresight of the originator/author's
  establishing the 'frame work', which initially bore no fruit.
One should see it organically, as a 'work in progress'.
If there's a structure so that the knowledge if various contributors
can be accumulated, there will be progress.
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.

== Chris Glur.

PS. I'd like to revive my project which went dormant when:
1. DOSEMU wouldn't drive par-port for my programmer,
2. I didn't get satisfactory feed back of how to use arrays.

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