Re: [Amforth] New Repository for everone

2014-03-04 Thread Sam Putman
In 2014 the decision is fairly simple: Do you need (merely) a version control system, or a social network? If the former, there are abundant, adequate options. The latter, Github is the only sensible choice, hence, git. This has almost nothing to do with technical advantages, it's just Metcalfe's

Re: [Amforth] GPL and AmForth

2014-02-19 Thread Sam Putman
On Wed, Feb 19, 2014 at 1:17 PM, Matthias Trute wrote: > Sam, > > > Matthias has the only opinion which matters, and is on record as strongly > > opposed to this sort of license. > > You seem to ask why? These licenses are like one-way roads. From the > vendor (me and a few other people) to all.

Re: [Amforth] GPL and AmForth

2014-02-19 Thread Sam Putman
On Wed, Feb 19, 2014 at 8:10 AM, Michael Picco wrote: > Thank you Paulo, for your succinct breakdown of information that > matters. Perhaps this will put an end to the somewhat incessant > yammering that's been going on for the last few days. Such apparent > in-fighting does nothing to advance w

Re: [Amforth] Dictionary names obfuscation

2014-02-18 Thread Sam Putman
On Tue, Feb 18, 2014 at 9:11 AM, Hannu Vuolasaho wrote: > First thing about topic. > > The language which you rae using is forth. it is obfuscated already to 99% > of people. :) > > Secondly it would be sad to lose Enoch from community who has given quite > many ideas. > > Thirdly about GPL. > >

Re: [Amforth] Dictionary names obfuscation

2014-02-17 Thread Sam Putman
On Mon, Feb 17, 2014 at 11:52 AM, Matthias Trute wrote: > Hi Sam, > I am concerned about part of what you appear to be implying here. Do you > > consider Forth words loaded into the AmForth environment to constitute > > 'derived works', and hence subject to the GPL? > > Definitely. Any program i

Re: [Amforth] Dictionary names obfuscation

2014-02-17 Thread Sam Putman
On Mon, Feb 17, 2014 at 8:33 AM, Matthias Trute wrote: > 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,

Re: [Amforth] ALSO

2014-01-27 Thread Sam Putman
On Sun, Jan 26, 2014 at 11:39 AM, Matthias Trute wrote: > > > Of course you'll blow the return stack pretty fast without tail > > call elimination. I confess I've looked at all the available Forths > > for the AVR so I can't remember if AmForth provides this > > capability. > > The amforth compil

Re: [Amforth] ALSO

2014-01-26 Thread Sam Putman
On Sun, Jan 26, 2014 at 8:39 AM, Enoch wrote: > Hi Matthias, > > Matthias Trute writes: > > > >> Their forward reference implementation is here: > >> openfirmware/forth/kernel/forward.fth > > > > I don't understand the code. > > > >> > >> Should we do likewise? > > > > DEFER is "good enough". >