Inside this repository we develop the core tools of the ABS modelling language. The current language manual is at https://abs-models.org/manual/.

See https://abs-models.org/getting_started/ on how to install or compile the tools.

• frontend - the ABS compiler and runtime support. See https://abs-models.org/getting_started/local-install/ for installation instructions.

• abs-models.org - Source for the https://abs-models.org website. See the README.org file in that subdirectory for deployment information. DEPRECATED: content will be moved below website/ and put under sphinx.

• abs-docs - the ABS language manual, available online at http://abs-models.org/manual/. To generate the manual locally, run make manual. DEPRECATED: asciidoc content will be moved below website/ and maintained with the rest of the website.

  • abs-docs/ReferenceManual - an older LaTeX ABS reference manual, now mostly of historical interest

  • abs-docs/Ott - a formal grammar for a large subset of ABS, written in Ott

• org.abs-models.releng - Files used by Jenkins and Buckminster for continuous integration at https://envisage.ifi.uio.no:8080/jenkins/.

• abs-unit - demonstration, description and initial ideas about the ABSUnit (a unit testing framework for ABS) (with Maven dependencies management)

• various leftovers from previous projects, to be evaluated and reactivated or pruned

Please clone the archive without line ending conversion (unfortunately activated by default on Windows). Use -c core.autocrlf=false as argument for the initial git clone command, i.e.,

git clone https://github.com/abstools/abstools -c core.autocrlf=false

Otherwise, running the tools inside Docker will fail with obscure error messages.

Consider rebasing instead of merging your changes:

git pull --rebase

This avoids spurious "merge branch to master" commits.

git pull --rebase will, in case both you and the remote repository have new commits, replay your local commits on top of upstream changes instead of adding a new local commit that merges the master and origin/master branches. Conflicts have to be resolved per patch (via git add + git rebase --continue) instead of in one go, but we get a cleaner history.