On Nov 3, 2007, at 11:39 AM, Anton Ertl wrote:
Dennis Ruffer wrote:
1) arch/power/paper
It would be good to generate and keep the asm_disasm_paper.pdf in the
repository. It provided me a good example to get my LaTeX support
working, but others should not have to do that.
We generally only keep source files in the repository, not generated
files, even for essential generated files like engine/prim.i. We do
supply many generated files in the distribution.
Concerning this document: Currently I do not intend to include this
with the distribution. This is in the repository only because we have
it and I don't want it top get lost.
What do you find interesting about it? Maybe we should put these
parts into the Gforth manual.
Knowing what Michal was thinking when he wrote the PPC assembler is
useful when trying to deal with what it does, or doesn't do. Knowing
how it was tested, and what his development environment was helps
when doing regression testing. Basically, documentation from user
submitted extensions should probably find its way into the main
documentation, eventually.
3) additions to engine/.cvsignore
done, except:
engine.i
That's not a file we generate.
Hmm, wonder where it can from then. I don't recognize it either, but
so far, it doesn't seem to hurt anything to be gone.
6) change to config.guess to work on Intel Macs
I have updated config.guess and config.sub to the latest versions
(from <http://cvs.savannah.gnu.org/viewvc/config/config/>). I hope
that these now support Intel Macs (I cannot check).
I'll try to find some time to test it again next week. Maybe (se below).
In case you are wondering, the .project
file in the root is Eclipse's addition.
I guess you should put that in the .cvsignore in your home directory.
You are right. I just have to figure out how to do that better.
Is anyone else using Eclipse with Forth yet? It is becoming my
favored IDE and I suspect, it may become even more important for the
work I am doing in the future. Fighting the onslaught of Forth IDEs
in the Windows environment is starting to become important.
I am probably too used to Emacs to switch to another IDE, but I would
love to see a demo of Eclips with Forth. Maybe at the next EuroForth
in September 2008 in Vienna? :-)
I'm trying to get over to EuroForth, someday. So far, the financial
gods have not aligned in that direction. ;)
BTW, for anyone checking out Gforth right now: libcc.fs is not working
currently.
Hmm, maybe I'll wait on updating then. Does this affect the external
library calls? I use them extensively now. Although, this has
always been broken on the Intel Macs. I'm using a ppc compile on
those systems right now, letting Apple's Rosetta handle the
conversion. Are you getting away from the ffcall interface or have
they fixed the Intel Mac problem yet?
- anton
DaR
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
