DSlib Reference

The plan on versioning is:

Every module has a version:
Before it's intended for use, it's marked as experimental, and zer0ver
```
is done.
```

After some time, if the module is usable, the version jumps to 1.0.0, from

there on:
* If compatibility is very badly broken, the version jumps to &lt;maj+1&gt;.0.0.
  The new version is then loaded via dslib.mrequire("&lt;modulename&gt; &lt;maj+1&gt;"),
  and the old version stays available, if possible.
* Otherwise, if a new feature is introduced, the version jumps to &lt;maj&gt;.&lt;min+1&gt;.0.
* Otherwise, if something worth an update happened, the version jumps to
  &lt;maj&gt;.&lt;min&gt;.&lt;patch+1&gt;.

DSlib as a whole has a version:
The major version stays at 0 until it becomes 1. Then it stays 1.

Whenever one (or more at once) modules increase their major or minor version

number, the minor version number of DSlib is also incremented by at least 1.

Whenever one (or more at once) modules increase their patch version number,
```
the patch version number of DSlib is also incremented by at least 1.
```
As nobody enforces me to do this, it is likely this won't happen in practice for now.

TODO: find out how to make this look good in ldoc

DSlib

Topics

Modules

Examples