Hello Matthias, Matthias Trute <mtr...@web.de> writes:
> Hi Enoch, > > >> Please find in <http://pastebin.com/BRHaitj9> my complete CRC-8 >> implementation >> for peer review and library inclusion if there is interest. > > Since you put your code under MIT license, there is AFAIK > no legal way to combine it with amforth (GPL). IANAL && IMHO. According to <http://en.wikipedia.org/wiki/MIT_License>: "The license is also GPL-compatible, meaning that the GPL permits combination and redistribution with software that uses the MIT License". Broadcom Corp. chose MIT License when contributing crc8.c/crc8.h to the Linux kernel. I was simply following their example :-) *Still*, if you feel strongly that anything incorporated into the Amforth system must be released under GPLv2 I will respect your decision! By the way, I recommend that thought is given to encourage Amforth use in commercial (proprietary) designs. This is important if you wish to draw in professional developers (for their skills and opening up financial support opportunities). Even as things stand there is a way to "marry" GPL with proprietary code which is described here: <http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem>. The basic idea is: "However, in many cases you can distribute the GPL-covered software alongside your proprietary system. To do this validly, you must make sure that the free and non-free programs communicate at arms length, that they are not combined in a way that would make them effectively a single program." Still, as the copyright holder you have the power to modify the license to facilitate certain Amforth usage. I will expand if you are interested. >> PS1: Is there any reference implementation for [if] [else] [then]. I need >> them >> and would be ready to help if needed. > > The file included was the reference implementation. I have no plans > to implement these words in the near future (had no use for them for > years). Hmm... giving up on something useful as this one: [undefined] rdrop [if] : rdrop r> drop ; [then] You wouldn't turn down a helping hand, would you? :-) >> PS2: I assumed that my amforth-shell.py patch was accepted :-) > > I hope, Keith would comment on it as well. Another strategy for > the constants would be to read the files twice. The first pass > extracts the constant definitions and the second pass uses > them. If the replacement really saves code space (every literal > uses 2 cells in the dictionary). As you recall my first attempt to patch the shell was quick yet too "dirty" (direct incorporation of Python dictionary, yuk :-). This local appl_defs.frt is cleaner. It's not just code saving that I am after. I want to keep WORDS shorter. I want to encourage future library submissions to be configurable (*). Regards, Enoch. (*) and here I need to highlight again the need for bracketed conditionals. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
