Erich Wälde writes:
> Enoch,
>
>
> Enoch writes:
>
>> writes:
>>
>>> Enoch,
>>>
>>>
>>> I repeat, I am not going to get into a licensing debate with anyone, but I
>>> believe I have satisfied the GPLv3 requirements.
>>>
>>>
>>> DaR
>>>
>>
>> I don't question your compliance Dennis, I leave that
> Since you're not the only one with a large project, I took the freedom to
start a new major section on the website: called "commented projects".
I'm interested. Do you have a link to the section? Myself, I've used
AmForth for a wild cranberry bog sensing network:
http://hub.darcs.net/pointfree/c
Enoch,
Enoch writes:
> writes:
>
>> Enoch,
>>
>>
>> I repeat, I am not going to get into a licensing debate with anyone, but I
>> believe I have satisfied the GPLv3 requirements.
>>
>>
>> DaR
>>
>
> I don't question your compliance Dennis, I leave that task to the
> copyright holder :-)
>
> Un
writes:
> Enoch,
>
>
> I repeat, I am not going to get into a licensing debate with anyone, but I
> believe I have satisfied the GPLv3 requirements.
>
>
> DaR
>
I don't question your compliance Dennis, I leave that task to the
copyright holder :-)
Unfortunately, anything *original* that you wi
Enoch,
I repeat, I am not going to get into a licensing debate with anyone, but I
believe I have satisfied the GPLv3 requirements.
DaR
From: Enoch
Sent: Saturday, May 9, 2015 2:34 PM
To: amforth-devel@lists.sourceforge.net
Dennis,
I would like to caution you that AmFort
Dennis,
I would like to caution you that AmForth nowadays is GPLv3, i.e., "most
toxic" :-)
I forked AmForth and continued with my independent AmForth-Shadow
development when Matthias made the switch from GPLv2 to GPLv3. My new
stuff is FreeBSD like licensed.
Cheers, Enoch.
https://github.com/w
Matthias,
I'm not going to get into a licensing debate with you. I prefer MIT and you can
choose whatever you prefer. I have published coinForth and forked a copy of
your amforth-5.8 into it. I also just published my docs with it. You can read
all about my attempts to compare amforth, SwiftX a
Dennis,
> I just need to find time to work out the compatibility issues and get
> my LyX document printing again and I will publish the update, probably
> within my coinForth repository, since amforth’s GNU license requires
> it. Then the source code will be more accessible too.
Since you're not
> > Maybe a simple edit to the Makefile could correct that issue.
>
> Since I use ant (and the build.xml files) I welcome feedback for the
makefiles. I seldom (in fact never) use > make.
Foolishly sloppy language from me again: I meant "Makefile" as a form of
synecdoche for "the Build Process."
Am Montag, den 20.04.2015, 22:17 -0500 schrieb Tom Maynard:
> > Can't someone here with a working Arduino Uno R3 help Steve?
>
> I haven't looked, but at least at the release level when I downloaded my
> first Amforth (v5.3?), there were HEX files for all supported hardware
> buried somewhere in t
Thanks for the praise! 😉
I just need to find time to work out the compatibility issues and get my LyX
document printing again and I will publish the update, probably within my
coinForth repository, since amforth’s GNU license requires it. Then the source
code will be more accessible too.
I m
> Now, to update http://www.forth.org/svfig/kk/02-2014-Ruffer.pdf
A Literate Program! Good golly, I didn't think there was anyone else in the
world who did this. So it's true that "No Man is an Island" after all.
A very nice piece of work, too -- and exactly what the community needs. Thank
y
Don't know if Steve ever got something working, but having been in his shoes,
and just recently stumbling upon a solution for my setup, I posted my setup
last night at: https://github.com/DRuffer/coinForth.
It's not the same board, but effectively, the same setup.
I also thank Steve for menti
> Can't someone here with a working Arduino Uno R3 help Steve?
I haven't looked, but at least at the release level when I downloaded my
first Amforth (v5.3?), there were HEX files for all supported hardware
buried somewhere in the distribution. Is that not true now?
Memory says that the HEX file
gp2 writes:
> Hello Mathias,
>
> I was surprised to read how you felt about my last post. I did not mean
> it as a criticism of you or your work at all!
>
> I was not crying out in frustration, but listing problems I encountered,
> Many of them had nothing to do with Amforth -- the Atmel IDE for
Steve,
English is (according to Oscar Wilde) the common language
that separates English an Americans, so I certainly expect
a whole bunch of misunderstandings for non-native
speakers like me. But sometimes... So I beg your (every
native speaker's) pardon for my English. English is *not* my
prima
Hello gp2, hello all,
so I chime in late, but nevertheless.
1. The road to amforth on controller X
Yes, that road is definitely long and windy. I sometimes give
classes on exactly that. There are so many pieces that *must*
work together, before the first ok prompt shows up.
You did a great job,
> "FORGET is not implemented
Um, yes: my note was incredibly poorly worded. I should have said something
like, "'FORGET' -- which in Amforth is implemented using 'MARKER.'" But,
too late now: you found it and figured it out.
> I assume I have to add MARKER by including it and burning a new inst
Thank you Tom,
doing more reading I found this:
"FORGET is not implemented since it would be nearly impossible to reset
the search order word list with reason-
able efforts. The better way is using MARKER from the library."
And so I assume I have to add MARKER by including it and burning a new
I am certainly no expert, but I can answer this question:
> 3.) Where is the erase function for practice code, or do I have to
> re-flash a new version of AMFORTH every time to get rid of old code?
You need to build your Forth image and include the FORGET word. Read the
doc (which is quite help
Hello Mathias,
I was surprised to read how you felt about my last post. I did not mean
it as a criticism of you or your work at all!
I was not crying out in frustration, but listing problems I encountered,
Many of them had nothing to do with Amforth -- the Atmel IDE for
instance, or AVRdude probl
> From: mtr...@web.de
> To: amforth-devel@lists.sourceforge.net
> Date: Tue, 14 Apr 2015 21:04:10 +0200
> Subject: Re: [Amforth] AMFORTH 5.8 on Uno R3
>
> Steve,
>
> I like it to get the un-modified first frustration
> fr
Steve,
I like it to get the un-modified first frustration
from people absolutely new to amforth. Really. My
first reaction to your mail was get lost (well,
something less polite in fact).
Now I think about what went wrong. Amforth is nothing
I am ashamed of. That may surprise you, but it defini
Hello,
As a new user of Amforth, I just wanted to give some feedback on trying
to implement 5.8 on an Arduino Uno R3 board.
I had quite a bit of difficulty and it took research over a couple of
days to get FORTH running. Here are some of the issues (and missteps on
my part) in hopes that they
24 matches
Mail list logo
