Changes http://wiki.axiom-developer.org/AxispBranch/diff
--
Axisp is an experimental branch of Axiom.  The focus of development is
to rewrite the original Boot implementation into Common Lisp, and to
improve and document the compiler and interpreter in the process.
Stephen Wilson is the principle maintainer.

There are two macroscopic stages involved:

- Semantic translation: Converting from Boot to Lisp is not hard.
The intention is that `connected components' of the system will be
converted into Lisp and documented.

- Design translation: Converting from Boot to Lisp is not pretty.
Once a `connected component' has been resolved, translated, and
documented, options for redesign will be considered.

AXISP IS AN EXPERIMENTAL BRANCH.  Some sub-branches of Axisp are
intended to be stable, others, er, not so much.  See the Project
Overview below.


Getting the Axisp Branch

  Axisp is available through a public Git repository on
  axiom-developer.org.  If you have an account on axiom-developer,
  simply invoke::

     git-clone ssh://<your-login>@axiom-developer.org/~swilson/axisp

  Alternatively, the user `git' can be used as a guest login with
  password `linus'.

  The above will give you a copy of the Axisp source tree rooted under
  the directory `my-axisp'.


Building Axisp

  Assuming the source tree is under $AXISP, do::

    \$ cd \$AXISP
    \$ export \$AXIOM=`pwd`/mnt/linux
    \$ export \$PATH=\$PATH:\$AXIOM/bin
    \$ make


Repo Overview

  After doing a git-clone, your repository should have the following
  remote branches:

   - origin/axisp :

       Staging ground for highly experimental code eventually looking
       for promotion into master.  Here, all bets are off.

   - origin/master :
  
       This is the stable axisp branch.

   - origin/axisp-silver-test :

       Staging ground for code looking for public review and promotion
       into axisp-silver-release.

   - origin/axisp-silver-release :
 
       Stable, tested code with changes intended to be pulled by Tim
       upstream into Silver.  This branch should almost always be a
       pristine image of Silver.

  Roughly speaking, code filters down through the above chain of
  branches.  Certain changes (for example fixing Boot bugs or
  documenting Boot code which resulted as a byproduct of the Lisp
  rewrite), are redundant to the master and axisp branches.  These types
  of changes go directly into axisp-silver-test or, if the change is
  trivial, into axisp-silver-release.

--
forwarded from http://wiki.axiom-developer.org/[EMAIL PROTECTED]

Reply via email to