> > 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."
> 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
> 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
> "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
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
