wren

The language itself might be quite different, but a few of the design parameters remind me of Wren[1], another language that's on my "try to embed it somewhere" list... [1]: https://github.com/munificent/wren

What I do is split the makefile in two. There's a top level makefile with targets like "make debug" and "make release". Those invoke a secondary makefile that actually builds things and takes options on the command line. That way I can build different configurations to different directories without having to copy/paste all of the rules for each configuration of each file. For example, the main makefile for Wren[1] has rules like: debug: @ $(MAKE) -f util/wren.mk MODE=debug That util/wren.mk [2] then uses "MODE" and a few other options, like: # Mode configuration. ifeq ($(MODE),debug) WREN := wrend C_OPTIONS += -O0 -DDEBUG -g BUILD_DIR := $(BUILD_DIR)/debug else WREN += wren C_OPTIONS += -O3 BUILD_DIR := $(BUILD_DIR)/release endif It has the real rules for compiling files:

If you just want a GC, here's a tiny one I wrote: https://github.com/munificent/mark-sweep And an article I wrote about it: http://journal.stuffwithstuff.com/2013/12/08/babys-first-gar... This was the inspiration for uLisp's GC (http://www.ulisp.com/show?1AWG). :) If you want a more full-featured but still small language in C, you could take a look at Wren: http://wren.io/ https://github.com/munificent/wren

No Go yet, but a couple: https://github.com/munificent/wren/wiki/Language-Bindings

I actually use negative indices in real code[1]. If you implement a stack using an array and you track the top of stack by a pointer just past the last element, then you can index negatively into that pointer to access items on the stack: // Create an empty stack. int stack[100]; int* top = &stack; // Push a couple of values. *top++ = 123; *top++ = 456; // Peek the values. printf("%d\n", top[-1]); // 456. printf("%d\n", top[-2]); // 123. You could make the pointer arithmetic more explicit like this: printf("%d\n", *(top - 1)); // 456. But I think that's needlessly verbose. [1]: https://github.com/munificent/wren/blob/master/src/vm/wren_v...

> I was inspired by the size of Lua's VM, but deterred by its obscurity (and lack of inline documentation), so my original goal was to create a very clean and minimal VM. Me too, so I created Wren: https://github.com/munificent/wren It's about the same size as Lua, significantly faster, and much more thoroughly documented. I also like the language itself more — it's object model is more familiar to someone coming from Java/C++/C#/etc. — but that's personal preference. ... heh and then I scroll down and see two people have already mentioned Wren. I guess I'm doing a good job of branding it as the "better documented Lua". :)

Take a look at Wren: https://github.com/munificent/wren

In the same vein: https://github.com/munificent/wren