Hi Everyone, This doesn't mean Amforth doesn't have a place in my research but will have a different role (used for benchmarking) on a totally separate riscv processor (probably on ESP32-C6) and will not be directly interfaced (linked in) with my intended application. I already have a forth (MIT licensed) that is interfaced with the CH32x033 version of my prototype application. The above forth has no connection to AmForth other than being another version of forth (MIT licensed). All this is part of the research and is definitely experimental, I am hopeful that all parties involved will benefit from this effort.
Regards, John S On Mon, Feb 9, 2026 at 6:58 AM John Sarabacha <[email protected]> wrote: > Hi Carsten, > Thank you for your input on this, which I totally agree, a simple fix > a name change and sorting out what belongs to AmForth and what belongs > to the body of work called forth that isn't GPLv3 licensed. > > Thank you again, > John S > > On Mon, Feb 9, 2026 at 4:12 AM Carsten Strotmann via Amforth-devel < > [email protected]> wrote: > >> >> Sorry, my mail client got the quoting wrong, 2nd try: >> >> Hi, >> >> On Monday 09 February 2026 01:54:25 AM (+01:00), John Sarabacha wrote: >> > Hi Erich and everyone, >> > As far as I understand, the derived work may still be published as >> GPL, >> but not any more permissive, >> > *if any of the used sources> are explicitly licensed GPL.* >> > See the underlined (above), >> > That is the point here, AmForth has 118 primary words (in my version >> in >> dict_prims.c), these words can be used to build the entire >> > AmForth system. I will only be using the primary words that are in the >> public domain (or not original works). Public domain works cannot >> > be licensed as GPLv3, just as you cannot relicense anybody else's >> licensed works (if only I had this kind of power - I could control all >> > software ever produced). >> >> If it doesn't contain traces of amForth, it then should be not named >> amForth or AmForth, as it will be something different. Using the same >> name >> for two completely different things would be confusing. >> >> If it does contain traces of amForth, it should be GPLv3 licensed. >> >> Greetings >> >> Carsten >> >> >> >> _______________________________________________ >> 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
