> Most of what I find written about Forth programming involves the
> basics; data stack, control structures, I/O, compilation. I'm
> interested in learning ways that complete non-programming-language-
> related applications (e.g. NOT Forth's written in Forth) have
> leveraged Forth's unique capabilities to solve problems differently
> from conventional practices.

> Specifically I'd love learning about anything having to do with:
> - Using Compile Time

>Specifically I'd love learning about anything having to do with:
>- Using Compile Time
>- Usage of Wordlists (how was a program structured? how were wordlists
>used? any app-specific abstractions that used wordlists?)
>- Featuring the data stack
>- Using the interpreter to process text files, or other text
>processing applications
>- Forth-style data structures
>- How a complex application was structured (how did you avoid name-
>collisions? any "scripts" compiled or run from within the
>application?)
>- Data storage implementation details (how memory and disk was used)
>- Extensions to the compiler
>- Modifications to the Forth system (extending the system into a new
>domain-specific environment)

>Most of what I find written about Forth programming involves the
>basics; data stack, control structures, I/O, compilation. I'm
>interested in learning ways that complete non-programming-language-
>related applications (e.g. NOT Forth's written in Forth) have
>leveraged Forth's unique capabilities to solve problems differently
>from conventional practices.

> What have circular buffers been useful for?

>> It's a good question. It would be helpful to hear what you *have* read,
>> so we know where you're starting from. Have you read "Thinking Forth"
>> (Google for it)? Although it's somewhat dated, it does address some of
>> these issues.

>
> I've read and own both Starting Forth and Thinking Forth. I treat
> them like bibles and re-read Thinking Forth for fun/encouragement
> often. Though the knowledge in them is starting to get a little
> stale ...

> roger.l...@gmail.com wrote:

>>> It's a good question. It would be helpful to hear what you *have* read,
>>> so we know where you're starting from. Have you read "Thinking Forth"
>>> (Google for it)? Although it's somewhat dated, it does address some of
>>> these issues.

>

>> I've read and own both Starting Forth and Thinking Forth. I treat
>> them like bibles and re-read Thinking Forth for fun/encouragement
>> often. Though the knowledge in them is starting to get a little
>> stale ...

>
> Starting Forth is very stale, particularly the paper copies (the online
> versions have been partially updated). Since you say you have
> SwiftForth, you have a copy of Forth Programmer's Handbook (pdf). You
> might benefit from Forth Application Techniques, and it's pretty cheap.
>

>>> Most of our application work nowadays is in embedded systems, which is
>>> reflected in my comments below.

> ...

> What have circular buffers been useful for?

> On Aug 29, 4:41 am, Elizabeth D Rather forth.com> wrote:

>>>> We don't actually worry a lot about name collisions in applications. A
>>>> lot of application words are only used locally, and if there's a
>>>> different one somewhere the compiler will issue a warning. Sometimes we
>>>> just examine the other version, conclude there's no practical conflict,
>>>> and forge ahead.

>>> Ah, OK, so you don't try to make as many words as possible "global"?

>> They may be technically global, but only interesting within a particular
>> section of the code. I see no reason to be paranoid about global names
>> (or variables).

>
> Not paranoid, simply wary. :)