Hi again George,
You don't need to pummel me into submission here, I am a believer in pure
forth
 (some humor here). Actually I try to be impartial to the many incarnations
of forth.
I have many of them in my research, each one has its strengths and
weaknesses.
The problem is they all have different dialects, even though the words may
be
similar the functionality could be different, even a slight difference can
mean failure of
your application, that is the nature of a state machine, if you don't
supply the correct
sequence it will fail (like a combination lock).
Why AmForth? It tries to alleviate this problem with 2012 compatibility of
the forth language.
It is not perfect in this sense, but my requirements for perfection aren't
necessary for my
project GLANN at this point since it is still in the research stage
(experimental).

Hope this helps you understand my viewpoint,
I do however appreciate your comments,
John S


On Sat, Jan 31, 2026 at 11:24 AM John Sarabacha <[email protected]>
wrote:

> Hi George,
>
> >> Yes, I am a very big fan of Dr. Ting's approach. It is about 20 words in
> >> Assembler and the rest of Forth is derived in Forth.
>
> I do like this approach as well, preForth and seedForth did this starting
> with 13 words
> the only thing was it was using an i386 assembler which I didn't know well.
>
>
> Thanks for your comment,
> John S
> PS: Wisdom is proved by it's works (not my expression - from the Bible)
>
> On Sat, Jan 31, 2026 at 11:10 AM John Sarabacha <[email protected]>
> wrote:
>
>> Hi Brian,
>> I have not read his book, all that I know about him is that he was very
>> knowledgeable in his
>> field (using a C versions of forth) and yet was very humble (a good
>> thing) and he also coined the expression
>>  "trying to explain forth in forth is silly" (think that is what he said
>> or something like that). Also
>> when I reached out to one of his associates Brad Nelson he actually
>> responded with useful information.
>>
>> Thank you for your comment.
>> John S
>>
>>
>>
>> On Sat, Jan 31, 2026 at 9:51 AM George H <[email protected]>
>> wrote:
>>
>>>
>>> https://www.taaze.tw/products/11100495785.html?srsltid=AfmBOoqFPORunhEewSzHLNyzXcYQY7LKTM_MKo3ogALWeoqA9P9J4tI5
>>>
>>> I do realize that AmForth took on a different approach than C.H.Ting. And
>>> that standardized Forth has a long history of developement.
>>>
>>> But Dr. C.H.Ting simply does more with less.
>>>
>>> On Sat, Jan 31, 2026, 22:41 George H <[email protected]> wrote:
>>>
>>> > Yes, I am a very big fan of Dr. Ting's approach. It is about 20 words
>>> in
>>> > Assembler and the rest of Forth is derived in Forth.
>>> >
>>> > On Sat, Jan 31, 2026, 22:34 Brian K Navarette <[email protected]>
>>> > wrote:
>>> >
>>> >> All of the fun of forth on microcontrollers is learning as YOU, not
>>> some
>>> >> software package, interact with the device. You should (re)read Dr
>>> Tings
>>> >> book, The Arduino controlled by eForth to understand better why these
>>> >> forth
>>> >> systems exist.
>>> >> brian-in-ohio
>>> >>
>>> >> On Fri, Jan 30, 2026 at 11:16 AM John Sarabacha <[email protected]
>>> >
>>> >> wrote:
>>> >>
>>> >> > Hi Everyone,
>>> >> > AmForth is a good candidate for ML (Machine Learning) or AI. Better
>>> than
>>> >> > Python for front end in my opinion. Most work at this point is
>>> using C,
>>> >> > Python and assembler (pure or mixed asm(...)). There has been a lot
>>> of
>>> >> good
>>> >> > work already like expert systems (like CLIPS) that can be utilized
>>> to
>>> >> > generate forth. This is an area that I am actively pursuing. Now
>>> you may
>>> >> > see why I have taken this approach to making AmForth more usable
>>> with
>>> >> other
>>> >> > software tools.
>>> >> >
>>> >> > Regards,
>>> >> > John S
>>> >> >
>>> >> > _______________________________________________
>>> >> > Amforth-devel mailing list for http://amforth.sf.net/
>>> >> > [email protected]
>>> >> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>> >> >
>>> >>
>>> >> _______________________________________________
>>> >> Amforth-devel mailing list for http://amforth.sf.net/
>>> >> [email protected]
>>> >> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>> >>
>>> >
>>>
>>> _______________________________________________
>>> Amforth-devel mailing list for http://amforth.sf.net/
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>>>
>>

_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
[email protected]
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Reply via email to