cish VS kesh

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

I have something similar in kesh, where : is the assignment operator and the type/signature may be "assigned" before the value:

I'm not OP, in case you thought that :) kesh lives here. I tried incorporating some of the ideas discussed here, but posponed it to a later language, which I'm still thinking about.

This is a great idea that I've adopted for my PL. I took it a step further and also allow extensions of the core language to be specified, including profiles.

My (non-existing) language kesh, designed to compile to TypeScript, has expression blocks. That was one of my first decisions.

Still no work on a compiler, but more work on the documentation of kesh.

I'm working on kesh, but it's only at the design stage. I have tried to make it simple yet powerful, so I thought I'd mention it even though you can't use it.

I tried to distill down the most essential features of TS/JS (functional, prototypal) and then come up with new syntax and semantics that was minimal, orthogonal and hopefully easy to learn and use. The result is kesh and na.

I like the way you think. I had the same goal with kesh. A minimal syntax is easier on the eye and lets you focus on the actual code.

I'm only at the drawing board stage of kesh, a simple little PL that one day might possibly transpile to TypeScript. Not a single line of compiler code has been written so far, it's still all about syntax design and exploring ideas. kesh is mostly a pastime activity and something I can ponder over when I'm bored or can't sleep (which may be the reason I can't sleep).