This section has various external resources useful when using the Horse64 programming language. This includes the code location for all the core tooling, where to report bugs, etc.
If you want to get started, go here for the SDK (Software Development Kit) for Horse64 and Moose64.
Before you report a bug, you might want to check the standard library reference documentation and the 💬 community chat to verify if what you found is truly a bug or rather a misunderstanding.
To report bugs, here are the locations for core components:
Compiler bug reports (this includes both Horse64's horsec and Moose64's moosec).
Standard library bug reports for Horse64 (behavior of built-in libraries like opening files, etc.).
Syntax highlighting and other extra developer libraries bug reports.
If you are unsure where to file a bug, simply guess, the maintainers will move it around if needed.
If you're reading this, you found the documentation! If you got some offline copy, you can find the latest online copy of the Horse64 documentation here. There is also the online copy of the Moose64 documentation.
If you want to contribute to and change the docs, go look here:
Find the 🧬 documentation code for Moose64 here.
The core projects are dual-licensed under either a BSD-style license or the Apache 2 license, with the minor exception to that being the official artwork images. Read the respective license files for details, the licenses of the core projects are almost the same.
Read about the Developer Certificate of Origin here.
Please note we currently want to avoid AI code contributions.
For the respective other projects, check the LICENSE.md file for each. It's part of each project's code. E.g. here's horp's code.
For seeing all dependencies, horp license . can help you.
Example to check what the SDK includes:
Make sure horp is available on your system.
Open a terminal, go into the extracted code folder, and run:
horp license .
The standard library provides all the built-in functionality like opening files, parsing basic formats like JSON, and basic text formatting and so son.
For Horse64, the standard library is in the core.horse64.org package which is the same repository that also contains horsec.
Get the standard library by fetching the SDK.
For Moose64, the standard library is in the m64.horse64.org package.
This is the Horse package manager.
Get horp by fetching the SDK.
The official compiler for Horse64 code is a binary called horsec. It's written primarily in Horse64.
Get it by fetching the SDK.
Find 🧬 horsec's code here along with the other parts of the standard library.
Moose64 is a sibling language developed together with Horse64, particularly useful for handling C integration and low level code.
Check out the Moose64 website.
Here's the Moose64 standard library.
The official compiler for Moose64 code is a binary called moosec. It's actually just a slightly different build of horsec, they share the same code base.
HVM, the "Horse Virtual Machine", provides the runtime powering Horse64 programs. HVM is primarily written in Moose64 and using some [[C]( https://en.wikipedia.org/wiki/C_(programming_language) libarries.
Get it by fetching the SDK.
Find the 🧬 HVM source code here.
Read here about advanced technical runtime concerns.
Spew3D is the base library used for accessing operating system facilities, multimedia, and other base functionality, used by HVM. 🧬 Find its code here. While it can be used separately for any C program, it's maintained as part of the Horse64 project.
For info on how to contribute, read here.
For a full list of who worked on and created Horse64, check the contributors for the central packages:
And for Moose64 specifically: