Hi Enoch,
> Let's revisit the issue of Amforth relationship with proprietary designs > at a later time. You seem to hope for something ;) > If you strongly feel that all contributed code should be GPL licensed I > can live with that. I will send a correction to your web.de address. Great, thank you indeed. > I plan further code contributions. Even greater. You will be my hero ;) > What is your opinion about endorsing > a certain Forth style (my preference is the openfirmware style). A quick look at some source files does not reveal anything that should be done differently. As long as you dont use the gforth style.. (my impression from reading the gforth sources is that they love programming like this: : (foo) bar ; : foo (foo) baz ; ((foo) is never used (or even documented) elsewhere) I admire the work of the gforth people, but wrt code readability I try to beat them. Would you mind to write a few sentences what you suggest for a recipe? > Now > that we have a project specific configuration file (appl_defs.frt), how > about recommending all contributors to respond to, say, something akin to > python __debug__ constant which determines the extent of run-time tests. That would be fine, but will create objections from people that even do not like the amforth-shell for its python-ness ;) Matthias ------------------------------------------------------------------------------ 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
