Hi Everyone, As I mentioned before, I try to be impartial to the various forth implementations that exist, I have many of them in my research and abide by their licensing (and copyright). In my working years (still working in retirement) to provide for my family I had to program in many different languages (assembler, C, C++, java, basic+,python,fortran ...). Yet I was always fascinated by forth because like linux it was propagated through time by love and not by greed (well almost), and people that worked with it enjoyed that experience (including myself) and that should in itself tell you something. View forth in general as a body of work, each member of that body has a function (as in the human body, eyes, nose,feet, brain ...), and one member of that body can't say to the other "I don't need you" (image the brain saying that to the feet). Likewise in forth can one forth (implementation) with a certain function not need another forth which may have a different function? AmForth has a certain function in my world (in neural networks) just as the others do ESP32Forth (eForth) and FiveForths (by someone also from Canada). Physical networks (not simulated networks) can be used to tie together these different functions (a true neural network).
Regards, John S PS: The analogy (human body) above is not mine, it is also from the Bible. On Mon, Feb 2, 2026 at 10:50 AM John Sarabacha <[email protected]> wrote: > Hi Tristan, > This is for my appreciation for AmForth work already done that is used > for the GLANN® project. > The secondary words have been completed, it is now being reviewed and > being optimized and will be added > to the download when ready. > GPLv3 doesn't require the source for a derivative work be supplied if no > distribution of the work is occurring, which is the case here (so this > download is a courtesy). > Along with this courtesy the GLANN® project needs to protect its IP, so > some files cannot be included like the assembly abstraction layer (yes it > can be reverse engineered but that's not an issue). Also AmForth will be > acting like a gateway into the network by calling GLANN routines (or linked > into) and not the other way around, this way the source for GLANN project > doesn't need to be made available under GPLv3 when and if (firmware) > distribution takes place. > Anybody in the GPLv3 chain of work can call for the enforcement of this > licensing agreement, it is still unclear where the actual chain starts. > Maybe George's approach is better after all, being less complicated > overall (with deployment & licensing)??? > > Regards, > John S > > > > > On Sun, Feb 1, 2026 at 3:12 AM <[email protected]> wrote: > >> Hi John, >> >> Thank you. Much appreciated. >> >> Best wishes, >> Tristan >> >> >> On 2026-02-01 01:00, John Sarabacha wrote: >> > Hi Everyone. >> > In compliance with GPLv3, the AmForth source program(s) changes and >> > extensions produced (derivative work) and used by the GLANN® project >> > also >> > known as AmForth-GLANN will be made available at >> > dedicatedcomputer.ca/test . >> > >> > 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
