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.
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:
If you're reading this, you found the documentation! If you got some offline copy, switch to the latest online copy of the documentation.
All 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. Read the respective license files for details, the licenses of all 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.
The standard library providing all the built-in functionality in the core.horse64.org can be found in the same location as horsec.
Get it by fetching the SDK.
Find the 🧬 standard library code here.
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.
HVM, the "Horse Virtual Machine", provides the runtime powering Horse64 programs. HVM is primarily written in C.
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: