mc

One of the goals I have is to keep the required runtime absolutely minimal, as well -- I'm ok with the compiler inserting some user-defined code in the appropriate places to initialize or release values, but I'd like to avoid growing the required code in https://github.com/oridb/mc/tree/master/rt unless it's absolutely necessary. And yes, that ~60 lines per platform is really all that's needed. (And actually, I should be able to merge more of it for SysV platforms.) So, I've thought about a GC, but I'd really prefer not to have it.

> That said, my few wishes for a C replacement would be generics, methods, and namespacing. I think my pet language (Myrddin) actually has you almost covered. It doesn't have methods, but it does have traits, which allow similar things at compile time. https://github.com/oridb/mc You have an example of generics and traits here, in the std namespace: https://github.com/oridb/mc/blob/master/lib/std/htab.myr https://github.com/oridb/mc/blob/master/lib/std/iterutil.myr

The compiler on github https://github.com/oridb/mc.

Author here. If you've got any questions, I'd be happy to answer. I'm a little sad that this got posted before I had a chance to write a good tutorial and upgrade the documentation. So, imagine that this project was just about to step into the shower when Hacker News came knocking on the front door. "A package? I like packages but.. damn it. I'm not presentable yet." All the code in compiled binaries is in Myrddin, other than a few assembly stubs: There is no dependency on any installed library, although you can bind to C if you want -- for example, http://git.eigenstate.org/ori/cbind-example.git/tree/ But everything else is in Myrddin. For example, memory allocations: https://github.com/oridb/mc/blob/master/lib/std/alloc.myr Or regexes: https://github.com/oridb/mc/tree/master/lib/regex The various system calls are all here: https://githu

> Anyways, I’ve been learning some interesting things about OSX that I’ll be sharing soon. Nice, that should be amusing to read. OSX is a very strange system -- it has two system call APIs (BSD, and Mach), which respectively have some very odd holes. Some of the OSX syscalls return values split between 32 bit registers instead of in a single 64 bit register, while others don't. Some of them return things by value, even though the C API specifies out parameters. And so on. I've spent way too much time trying to figure out how this stuff works on OSX when writing Myrddin (https://github.com/oridb/mc). I've still got quite a bit more to do so that I can finish implementing libthread on OSX.

I have recently started using myrddin (compiler here https://github.com/oridb/mc ) as a c replacement. It is still changing fast but I think it could be great for writing games in the future.

You should also checkout myrddin, a new systems programming language sharing many features with rust and C. github: https://github.com/oridb/mc website: http://eigenstate.org/myrddin/

The level of dedication is required is really high. I stumbled upon https://github.com/oridb/mc and found my new favourite language written entirely by one person over the course of many years.

Bowing to popular demand, I also have a github mirror: https://github.com/oridb/mc/