interface99
tailspin-v0
interface99 | tailspin-v0 | |
---|---|---|
15 | 16 | |
262 | 32 | |
- | - | |
1.9 | 7.5 | |
about 1 year ago | 3 months ago | |
C | Java | |
MIT License | MIT 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.
interface99
- Full-featured OOP interfaces for C99
-
Templates in C
There is a project that achieves something like this, and quite nicely I think, worth checking it https://github.com/Hirrolot/interface99
-
Pretty-Printable Enumerations in Pure C
I agree; I would especially not recommend abusing macros throughout an application codebase too much. Conceptually, Metalang99 is more of a (sub)language than a library, which also adds some entry barrier. Ideally, I see the application of Metalang99 being used "behind the scenes", e.g., encapsulated in separate code files/libraries such as Datatype99 and Interface99. This is what I (mostly) do in SmolRTSP.
- Just Lua things
-
Comparing Golang and Interface99
There are also some differences. Golang, for example, can resolve interface methods at run-time, whereas Interface99 constructs virtual tables statically. Interface99 allows default implementations; Golang doesn't. And, of course, Interface99 mandates placing impl(MyIface, MyType), whereas Golang uses a.k.a. duck typing for interfaces (interface implementations are indistinguishable from ordinary methods). Also, when you would use embedding in Golang, such as this:
I think your github repo link is broken. Here's a working link.
-
lipstick: a Rust-like syntax frontend for C
I've done something similar with Datatype99 and Interface99. They are like a macro eDSL that compiles to C. The first one features algebraic data types, the second one features interfaces.
-
Any alternative to vala?
If you need a bit more high-level constructions, you can use the Datatype99 and Interface99 libraries. The former provides polymorphism over data, the latter -- over behaviour (I am the creator of these libraries).
-
Diamonds in the Rough : An Honest Trial for any Language
Is it possible that you could benefit from "a better C"? If so, I'd love to hear your take on Crystal, and the recent announce on Interface99.
-
Comparing interfaces: Rust and Interface99
There is a full example code: https://github.com/Hirrolot/interface99/blob/master/examples/state.c.
tailspin-v0
- What languages have you learnt with AoC and now you love...or ended as "meh"?
-
Advent of Code 2023 in your language
I eventually tend to do all days in Tailspin. The ones I have done so far are in directories ending in "tt" (the others are in Pyret, just to get a feel for it) https://github.com/tobega/aoc2023/tree/main
-
I have great difficulties
As a general tip, it is often helpful to first try to think of how you would like to represent the data in your program. Then you need to parse the data into that structure. I'd recommend you to look at a PEG-parser, for example. Or if you like, look at my Tailspin programming language which has a very visual parser syntax and also very visual ways of creating data structures (if that should happen to be your mental affinity). Look at my day1 for example. Or if you're more mathematical, maybe a functional language (I also did day1 in Pyret)
-
An idea for a language focused around RxJs
My Tailspin language is based on processing streams of values, you might want to look at it https://github.com/tobega/tailspin-v0
-
[2022 Day 7] Solved in three different styles
Many people had trouble with the day 7 problem. Paradoxically, good developers probably had more trouble. Here some of the difficulties are explained and implementations are provided in imperative, functional and OO styles, written in the Tailspin programming language.
-
What codebases have the best or most educational unit/integration tests when implementing a programming language?
I test almost entirely from my language, that way the tests are independent of the implementation. Currently the tests are implemented in java because that fits the interpreter implementation https://github.com/tobega/tailspin-v0/tree/master/test/tailspin/samples
-
August 2022 monthly "What are you working on?" thread
Finished off the implementation of typed and offset array indices in Tailspin
-
March 2022 monthly "What are you working on?" thread
I ended up enabling left recursion in Tailspin's composer (parser) syntax. Much cleaner calculator example now.
-
Diamonds in the Rough : An Honest Trial for any Language
I think it's possible that Tailspin might be suitable for you.
-
Introducing Skiff, a gradually typed functional language written in Rust
I think gradual typing is definitely something worth exploring more. I thought it was a shame when Dart abandoned that path. Have you seen Shen ? I guess my small offering, Tailspin, is currently evolving to gradual typing as well.
What are some alternatives?
COS - C Object System: a framework that brings C to the level of other high level programming languages and beyond
Argon - Argon programming language
smolrtsp - A lightweight real-time streaming library for IP cameras
never - Never: statically typed, embeddable functional programming language.
rps-tailspin - A rock-paper-scissors server written in tailspin
boba - A general purpose statically-typed concatenative programming language.
sps - Pre-Scheme to (GNU) C compiler written in Pre-Scheme
bluebird - A work-in-progess programming language modeled after Ada and C++
Cloak - A mini-preprocessor library to demostrate the recursive capabilites of the preprocessor
butter - A tasty language for building efficient software. WIP
datatype99 - Algebraic data types for C99
Odin - Odin Programming Language