All, I know that the above subject line is a red flag to some but to others it is a vital commercial concern to understand where the border line passes.
On this subject I wrote in amforth-shadow github: Matthias Trute, AmForth creator, believes that its GPLv2 license means that users are entitled to receive the source of any code which the developer has chosen to include in the distribution, whether this code has an AmForth origin or not. While the Shadow questions this claim (based on a reliable source) the Shadow recommends to abide by Matthias expectations and solve pesky commercial situations through obfuscation of the source code. See the new amforth-shell options --create, --conceal and --log. Now my own (independent) code looks something like the following (an excerpt from --log output) which satisfies my customer concerns. ^^31 constant ^^71 variable ^^70 variable ^^69 variable ^^8 variable ^^7 variable ^^6 variable ^^5 : ^^68 dup @ 63 um* 64 um/mod swap 31 > if 1+ then &120 @ + swap ! ; No starting of a (un)holy wars please! Do understand that if we wish to make AmForth into anything but a toy we should consider these issues. Thanks, Enoch. P/S A side effect, during development ": longer_names_reveal_more ... ;" should no longer be a Flash space threat. ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
