6 run a common lisp (SBCL, CMUCL, CLISP) starting in the current
7 directory. We also assume that a recent version of CFFI has been
8 installed and is ASDF-loadable. Probably should include a local copy
11 Step through ls-demo.lisp for a range of examples that will become
12 part of the test suite.
18 1. change directory into the CommonLispStat working directory.
20 3. follow the commands in the ls-demo.lisp file, i.e.
23 b. (in-package :ls-user)
25 d. (setf mytest (normal-rand 20))
28 and see if they work (basic CFFI functionality for external C
29 library, LIFT package for unit-testing framework to ensure run time
32 4. Tell me ( <blindglobe@gmail.com> ) if there is any thing wrong (or
33 if anything happens to work.
35 CMUCL and SBCL work justfine at this stage.
37 CLISP is finicky regarding the problems that we have with CFFI
38 conversation. In particular that we can not really do typing that we
45 See Doc/README* for history and design considerations
46 See Doc/INSTALL for getting this to work and run
52 Working on this with git:
56 git clone git://repo.or.cz/CommonLispStat.git
59 will pull the whole repository, and create a "master" branch to work
60 on. Probably, you don't want to use the master branch, but more to
61 use a topic-centric branch, so you might:
63 git checkout -b myTopicBranch
65 and then work on myTopicBranch, pulling back to the master branch when
71 git pull . myTopicBranch
74 of course, perhaps you want to contribute to the mob branch. For
75 that, after cloning the repository as above, you would:
78 git checkout -b mob remotes/origin/mob
80 <work, work, work... through a cycle of
83 git add <files just edited>
84 git commit -m "what I just did"
86 ad-nauseum. When ready to commit, then just >