Blade is a simple, fast, clean and dynamic language that allows you to develop complex applications quickly. Blade emphasises algorithm over syntax and for this reason, it has a very small but powerful syntax set with a very natural feel.
I currently lack a Windows device to test Blade on Windows. While I expect most features to work, I cannot guarantee that they do and therefore solicit the help of fellow and willing contributors who can actively test Blade on Windows devices.
Thanks!
- Simple syntax and minimal keywords.
- Dynamically typed.
- Fast.
- Comprehensive builtin functions.
- Object-oriented (only supports single inheritance for now. Multiple inheritance is open for discussion).
- Exceptions.
- Closures.
- Custom iterable classes.
- Garbage collection.
- Stack-based VM.
- REPL
- Lightweight.
- Highly portable.
Documentation is currently in-progress in the blade-docs repo. You can read the Blade language documentation online at bladelang.com.
| Directory | Contents |
|---|---|
benchmarks |
Contains the sample benchmarks for Blade (some are based on the Benchmark games). |
libs |
Contains the Blade standard library. |
src |
The source code of the Blade language including the native implementation of some Blade library classes and functions in the modules directory. |
scripts |
Helper scripts for various uses such as automated installation. |
tests |
A few test cases that Blade implementation must pass. |
thirdparty |
Contains open-source libraries and packages used by Blade |
Along with Blade's goal to be simplicity, flexibility and expressiveness is a strong desire to make the community around it as friendly and welcoming as possible. Therefore, all forms of contributions from pull requests, suggestions, typo fixes in documentation, feature request, bug reports and any contribution at all is greatly welcomed and appreciated.
WE NEED HELP! From review of this documentation, to suggestions on the core features of Blade, testing of Blade features, writing more comprehensive tests, bug detection, code fixes and more. PLEASE CONTRIBUTE!
The standard. The general workflow is as follows.
- Find/file an issue on the Issues tab.
- Fork the repo and make your changes.
- Push your changes to a branch in your forked repo. For coding guidelines, see the project README file.
- Submit a pull request to Blade from your forked repo.
You can also just mail your issues to Ore Richard Muyiwa directly.
-
I decided to break from the popular camel case common to C style languages and went with snake cases. Honestly speaking, the only justifiable reason is because I think it looks cool. I know you may have a differing opinion, but I will really appreciate it that you keep to that in your PRs. I used this same style for both the C source and the core library.
-
For formatting, simply follow the LLVM guide minus the whole braces
{/}on separate line thing. It looks really ugly. I advice you use the JetBrains CLion or Visual Studio Code IDE(s) to format your code before submitting for PR.
That simple!
