Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
The definitive manual on the ooc programming language
Makefile CSS Python
branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
_assets
_scripts
.gitignore Add an intro and number the chapters.
000-intro.md Wrap code blocks with `~~~`, pandoc-style.
001-constructors.md [001-constructors] Typo fix: DRI -> DRY.
002-covers-vs-classes.md Merge pull request #7 from cdrubin/patch-2
003-first-class-functions.md Add a new line at the top of each Markdown files, to avoid issues whe…
004-generics.md Add a new line at the top of each Markdown files, to avoid issues whe…
005-properties.md foo: Foo {} is not valid for preoperties
006-tuples.md Add a new line at the top of each Markdown files, to avoid issues whe…
007-version-blocks.md Add a new line at the top of each Markdown files, to avoid issues whe…
008-use-files.md Document .use files. Somehow.
Makefile Generate RST output.
README.md Made sidebar fixed, instead of scrolling with page.

README.md

the ooc language

status

In progress, send feedback to amos@lockfree.ch and mention 'ooc' in the subject.

Thanks a lot =)

Amos Wenger aka @nddrylliog

how to build the doc ?

Easy,

$ make

will generate a single-page, HTML version of the documentation.

Then,

$ make publish

will switch to the gh-pages branch, commit the modifications and push the commits to origin (which may be your forked repository).

todo

  1. Figure out how to order the sections.
  2. Merge branch 'mdoc' into 'master' in a way that will let us generate both versions of the documentation with a single Makefile.
  3. ...
  4. Profit !
Something went wrong with that request. Please try again.