cish VS Cwerg

The other day I was implementing an AST in Cish, when I realized I could leverage Cish's type-system to do the type checking for the AST automatically.

The latest release

Link to Github Release Page

Nice, although TeleClassic is a little different - it’s written ground up from just the stuff in .NETs stl, and I’m hoping this’ll provide the increased flexibility I want. Eventually I hope to use SuperForth, a language I wrote, as an in game scripting language which users can use to upload their own mini games.

Here’s the GitHub repo, and I recommend that you build with makefile.

machine.h

``` All of the above functions, with the exception of main, can be found in compiler.c.

I’m still working on SuperForth, a statically typed functional programming language. I’m currently working on reducing the memory footprint of the ast. Part of the reason it’s there is because the ast was designed before the virtual machine and compiler were implemented, so it’s kinda bloated at the moment

It’s pretty much high level c, but with anon functions and higher order functions. The original goal of the project was to provide higher level functional abstractions/a faster more portable runtime for running USACO solutions. Although it’s not nearly as fast as C, or even Java, it’s register based vm runs 3x as fast as python, with the same amount of portability. The compiler doesn’t apply many optimizations (it’s under 400 LOC), and the rest of the code is fairly short and simple to understand. check it out here

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