ooc-lang / the-ooc-language Public

📘 The definitive manual on the ooc programming language

ooc-lang.org/

Notifications

Name		Name	Last commit message	Last commit date
Latest commit History 66 Commits
_assets		_assets
_scripts		_scripts
.gitignore		.gitignore
000-intro.md		000-intro.md
001-constructors.md		001-constructors.md
002-covers-vs-classes.md		002-covers-vs-classes.md
003-first-class-functions.md		003-first-class-functions.md
004-generics.md		004-generics.md
005-properties.md		005-properties.md
006-tuples.md		006-tuples.md
007-version-blocks.md		007-version-blocks.md
008-use-files.md		008-use-files.md
Makefile		Makefile
README.md		README.md

Repository files navigation

the ooc language

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

Thanks a lot =)

Amos Wenger aka @nddrylliog

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).

Figure out how to order the sections.
Merge branch 'mdoc' into 'master' in a way that will let us generate both versions of the documentation with a single Makefile.
...
Profit !