sokol-odin
Odin
sokol-odin | Odin | |
---|---|---|
4 | 85 | |
61 | 5,752 | |
- | 4.4% | |
8.9 | 10.0 | |
5 days ago | 1 day ago | |
C | Odin | |
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sokol-odin
-
Odin Programming Language
* etc
There is also the second issue that C is technically TWO languages: the C programming language and the C preprocessor. People mix the two together and things cannot be easily translated. A good basic example of this is people using `#define` for constants, and thus that name has no semantic meaning in the language itself. A translator has to try and make some semantic meaning from the intersection of these two languages, even if people don't make a distinction when making APIs.
And Odin's `foreign` system allows [1] for a lot of really nice things that most other languages cannot do so tersely. Here are two examples of demonstrating bindings of C libraries that feel as if they were native Odin libraries WITHOUT any wrappers:
* https://github.com/floooh/sokol-odin/blob/main/sokol/gfx/gfx... (and the rest)
-
Nim v2.0 Released
I maintain auto-generated bindings for my C libraries for Zig and Nim (and Odin and Rust - although the Rust bindings definitely need some love to make them a lot more idiomatic).
I think looking at the examples (which is essentially the same code in different languages) gives you a high level idea, but they only scratch the surface when it comes to language features (things like the Zig code not using comptime features):
Zig: https://github.com/floooh/sokol-zig/tree/master/src/examples
Nim: https://github.com/floooh/sokol-nim/tree/master/examples
Odin: https://github.com/floooh/sokol-odin/tree/main/examples
Rust: https://github.com/floooh/sokol-rust/tree/main/examples
-
I think Zig is hard but worth it
I'm actually dabbling with Odin a bit in the scope of language bindings for the sokol headers:
https://github.com/floooh/sokol-odin
It's a very enjoyable language!
-
I like the Odin programming language
I recently wrote a bindings generator to Odin for my C libraries, and the FFI is very well thought out, down to defining things like linker dependencies in the code. For instance see here:
https://github.com/floooh/sokol-odin/blob/main/sokol/gfx/gfx...
The only minor downside (compared to Zig) is that Odin still requires a separate C/C++ toolchain to actually build the C dependencies. But I guess that's a typical 1st-world-problem ;)
(but AFAIK Odins FFI system isn't in any way related or depending on LLVM).
Odin
-
Giving Odin Vision
This article is about my experience with Odin programming language. So, I won't talk about its features and advantages and provide basic tutorials. There are plenty of materials on those topics.
-
Zig, Rust, and Other Languages
There's also Odin[0] too. I tried using them all and Odin was pretty nice. Nim is also good too but a lot more features.
But - I concluded that language matters a lot less compared to APIs. Yes, the language should have enough good features to let the programmers express themselves, but overall well designed APIs matter a lot more than language. For example -tossing most of the C stdlib and following a consistent coding style (similar to one described here -[1]), with using Arenas for memory allocation, I can be just as productive in C.
[0] - https://odin-lang.org
-
Odin Programming Language
I highly recommend looking at:
* The Overview: <https://odin-lang.org/docs/overview/>
* examples/demo: <https://github.com/odin-lang/Odin/blob/master/examples/demo/...>
As for the first example: a basic lexing example is probably boring, but it does show some basic ideas of what the language is about. If people want to write better examples or just reorder the current ones, please feel free to make an issue or PR on the website's GitHub page: <https://github.com/odin-lang/odin-lang.org>.
-
babel tree
I use Odin primarily, it’s C-level but pascal/Go syntax and inspiration https://odin-lang.org/
- Botlib: Telegram Bots in C by Antirez
- "Odin is a general-purpose programming language with distinct typing built for high performance, modern systems and data-oriented programming."
- Austral Programming Language
- Small Joys with Odin
-
Can't decide what engine/library/framework I want to master
Website: https://odin-lang.org/
-
Download Odin and get started today! Includes binding to popular video game libraries
Get it from the website: https://odin-lang.org/ -- Odin includes bindings to popular gamedev libraries & APIs such as Raylib, SDL, DirectX, OpenGL and Vulkan.
What are some alternatives?
linux - Linux kernel source tree
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
wayland - Core Wayland protocol and libraries (mirror)
v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
mvb-opencv - Minimum Viable Bindings to OpenCV for Nim
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
rust - Empowering everyone to build reliable and efficient software.
RFCs - A repository for your Nim proposals.
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
Beef - Beef Programming Language