minima VS Cwerg

Currently, I'm trying to migrate a project from MSVC to GCC to target different platforms aside from Windows. Using this makefile, a error: conflicting types for for all the methods defined in builtins.c and builtins.h. I'm using macros to define the functions so I suspect that has something to do with it.

Now to reproduce the bug, you have to run the contents of bug.txt. I ran it in REPL mode to see which specific line failed to execute (it’s the last line). Now inside one of the dependency files(the function sort_terms is where the bug occurred), I added the print statement to sorta approximate where it crashed.

The program that I am working on is an interpreter, Minima, and it’s compiled with MSVC. More specifically I’m working on a symbolic math library in Minima. The executable that crashed can be found here. Download all the files in the example folder with the executable, those mainly consist of the dependencies I was using.

I did write an AST to expedite the development time since I had initially thought that ASTs were not necessary, especially considering the nature of my languages syntax. However a lot of complications have arisen from trying to implement compiler optimizations without an AST. I was wondering whether there are some low hanging compiler optimizations that don’t require an AST to implement.

Minima because I fucking wrote it. It’s OO, functional, supports lambdas and anon functions, and it’s way faster that Python.

I’ve just finished writing Minima’s inheritance system. You can check out an example here . I’ve been trying to weed out all the bugs and make Minima super stable.

Minima now supports single-inheritance via the extend keyword. It resembles something akin to this example.

From my observations, inheritance seems to be highly discourage among the programming community Although inheritance and polymorphism in general is a powerful tool when utilized properly, I’m unsure as to whether the addition of polymorphistic features to a programming language that I’m writing, is a sound idea.

Perhaps these have already been dealt with and I'm missing critical information. If so, my apologies. Great work, in any case.

[1] https://github.com/robertmuth/Cwerg/tree/master/FrontEnd#dis...

Cwerg has backend that can be used as JIT and is written with readability in mind. Additional documentation can be found here: https://github.com/robertmuth/Cwerg/tree/master/Docs

I defined a basic ISA-like IR for Cwerg. It has unlimited registers and no constraints on immediates.

entire compiler front end ast nodes

I was also going down the path of bike shedding concrete syntax for my language Cwerg before pulling the plug on that effort and just using s-exprs. I managed to make the s-expr quite succinct by carefully choosing the order of arguments so I can omit optional ones. Also very helpful was to use square brackets for list, e.g. (call fun-name [arg1 arg2]). This simplifies parsing a little bit and is easier on the eye. Here are some Code Examples

I am iterating over the languages features for Cwerg's Frontend which aims to be a low level language with about the complexity of C but with some of the comforts of modern languages. I am especially happy with the choice of adding sum types. Relative to C the current feature set looks like this: Removed: * arrays decay to pointers * bitfields * separate compilation (more of a backend issue) * pre-processor * varargs * implcit type conversions * (untagged) unions * ++/-- * comma operator * implicitly nullable pointers * goto