Home of EO Objects

The term Objectionary was coined by David West in his great book Object Thinking, page 306. The original idea was to have a place where objects are hosted. Not libraries or software packages, but individual objects. This is exactly what this repository is about: it hosts EO objects. More details in this blog post.

When you are ready to publish a new object to this repository and make it visible for users of EO, you just create a new .eo file and place it in the right location, in one of the sub-directories inside the objects directory. For example:

text objects/ org/ eolang/ number.eo

Then, you add a meta to your object code, mentioning the location of the runtime package, where all necessary atoms are available. For example, you create a new random numbers generator:

```text +package org.example +rt jvm org.example:example-runtime:1.0

Random numbers generator.

[] > random [max] > next-int as-int. > @ mul. max ^ [] > @ ? ```

The meta +rt clearly points us to the place where a JAR with the class for the org.example.random.@ atom can be found.

When ready, submit a pull request to us. Our scripts will try to build and test all objects, together with your new one, to make sure you didn't break anything and your objects work together with your atoms. Then, we'll merge it and the repository will be updated. All users will be able to use your objects.

How to Publish a Library

Once the library is ready for publishing (i.e. all required changes are released) it can be published. Publishing includes several steps.

Create a new Git branch from this repo to get the latest changes.

There is a Bash script pull.sh, which may help you publish the entire library. In order to use it, you should first configure your library so that it publishes its full list of EO objects on each release into its gh-pages branch.

Then, when ready, run the script this way inside your local clone of this repo:

bash ./pull.sh objectionary/eo-files

Here, objectionary/eo-files is the name of the GitHub repository you are trying to publish. The script will pull all the necessary .eo sources from the repo and put them into the right places.

If several libraries need to be published, repeat this step for each of them.

Library objects within Objectionary must not contain any puzzles, so they need to be removed from pulled objects.

Next, the build needs to be verified. To do this, run the following:

bash make clean make

If the build fails, the issues need to be resolved.

If the build is clean, commit the changes and push the branch. Then, submit a pull request. Once your pull request is merged, all EO programmers will be able to use your library.