Matthias Trute writes:
> Hi,
>
>> SwiftX won't let you modify itself.
>
> You obey their license terms?
>
>> I took AmForth and changed it to fit
>> my needs (everyone's needs, IMHO) and of-course made the derived code
>> publicly available via AmForth-Shadow.
>
> I appreciate it. That some of y
Hi,
> SwiftX won't let you modify itself.
You obey their license terms?
> I took AmForth and changed it to fit
> my needs (everyone's needs, IMHO) and of-course made the derived code
> publicly available via AmForth-Shadow.
I appreciate it. That some of your ideas didn't go
into amforth does n
ome washing machine maker-robots with GPL code, provided code and
>> they have been happy. And company where I made this has still support
>> contract.
>>
>> > To: amforth-devel@lists.sourceforge.net
>> > From: i...@hotmail.com
>> > Date: Mon, 17 Feb 2014 18:4
e I made this
> has still support contract.
>
>> To: amforth-devel@lists.sourceforge.net
>> From: i...@hotmail.com
>> Date: Mon, 17 Feb 2014 18:44:53 -0500
>> Subject: Re: [Amforth] Dictionary names obfuscation
>
>> Changes to your kernel I make constantly publi
ppy. And company where I made this has still support
> contract.
>
> > To: amforth-devel@lists.sourceforge.net
> > From: i...@hotmail.com
> > Date: Mon, 17 Feb 2014 18:44:53 -0500
> > Subject: Re: [Amforth] Dictionary names obfuscation
>
> > Changes to your kern
net
> From: i...@hotmail.com
> Date: Mon, 17 Feb 2014 18:44:53 -0500
> Subject: Re: [Amforth] Dictionary names obfuscation
> Changes to your kernel I make constantly public (amforth-shadow on
> github) but "my dishwasher code" which a customer pays to develop I
> cannot disclose.
You
Dear Matthias,
Let's not lose our cool :-)
Changes to your kernel I make constantly public (amforth-shadow on
github) but "my dishwasher code" which a customer pays to develop I
cannot disclose.
My customer is obliged to maintain and upload my code separately to each
board they produce, boards
Matthias,
I am new to this list, so you can ignore me as you like, but I have been around
this industry for a very long time. I have discussed this topic and how it
relates to Forth all too often, but in the end, it really doesn't matter what
you and I think, or who is on the “right” side o
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
Enoch,
> If working with GPLv2 would have required the developer to disclose
> his/her underived and independent code Linux would not have become so
> popular at the core of commercial products as it is...
Have you ever heart of busybox and its court battles? They won
all of them, got all sources
Hi Sam,
> While far from interested in code obfuscation, the ability to write
> 'headless' words would free precious Flash for more applicative code.
:noname is made for headless words. A source code obfuscater
should be made outside amforth itself. IMHO a trivial exercise for
a search/replace on
On 02/17/2014 08:07 PM, Sam Putman wrote:
> On Mon, Feb 17, 2014 at 8:33 AM, Matthias Trute wrote:
>
>>> Enoch wrote:
>>>
>>> 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??
>
Dear Matthias,
I am first to appreciate your contribution for creating AmForth and I
sincerely don't want to even sound disrespectful but it seems to me that
you need to get educated on Open Source Licensing and the GPL in
particular.
If working with GPLv2 would have required the developer to dis
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,
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.
>
>
Dear Matthias & All:
I have been requested by my customer to try to make my AmForth code more
difficult to "SEE". 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
16 matches
Mail list logo
