Hi Enoch, > I have been requested by my customer to try to make my AmForth code more > difficult to "SEE".
See below > So, how do you feel about splitting the dictionary > space into two segments -- one for "growing" code, one for "growing" > names with the option of forgetting the latter. > > I must say that there is an element of Flash space saving in this > suggestion too. > > What's your opinon? Won't do. > P/S Let's start no GPL wars here. I'm not talking about code falling > under the GPLv2 license. You have told your customer, that amforth is GPL'ed, havn't you?? So if (s)he uses amforth, the source(s) of any derived work must be available upon request, There will be no battles to fight here, not even a (further) discussion, GPL is accepted by many courts worldwide, even in the US. Roma locuta causa finita. Matthias ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
