Edit "herkforth_source_code

edit "herkforth_source_code_management" below.

Tips:

The first line is the page title.
Separate your paragraphs by at least one blank line.
To have a < in your text, enter <<.
To make a link put <l and <> around the wiki page name or web address. Like this: <lmy page<> NOTE: that's a lowercase ELL
To learn about other things you can do please see wiki syntax

herkforth source code management

There are a couple ways to keep track of your code changes in <lherkforth<>.

Firstly you can press SHIFT-S to bootstrap and save. This compiles a forth
kernel and saves that, the dictionary, data, and source to a new ELF file. You
will get some strange file names if you do this too many times.

Secondly you can export the sources to a bunch of ascii files. (See <lherkforth
export source<> for details.)

There are a couple little scripts to help work with these files. One called
<c./changes<> shows you a universal diff of the differences between the files
in the <cblocks/<> directory and in the <cout/<> directory. You can apply these
changes to the <cblocks<> directory (where they can be used to <lbuild
herkforth<>) with <c./apply<>

Note: the ./changes and ./apply scripts ignore changes to variable values. This
only seems to cause trouble when you add a new block with the <cnew-block<>
word. In this case you will have to make sure the change to <cnum-blocks<>
carries through to <cblocks/000<>.

There is a handy script <c./t<> which attempts to run the most recent version
of the source you have around, and clear out the clutter from previous
versions. Note that it will delete forth? if any of the dependancies for
building herkforth000 are changed.

If you make changes that you would like to see in the main version of herkforth
<lcontact Jason Woofenden<>

Anti-Robot: Please enter your favorite four digit number here: