xic VS AECforWebAssembly

I cloc'd two compilers for xic, compilers written by cornell students for a compilers class which compile a toy C-like language down to assembly, possibly with some extensions. One compiler was about 11k sloc, the other about 32k. Both compilers are written mainly in OCaml, which is a terse language that is pretty optimal for compiler development, but have some java code in them as well. I think these are good examples of mostly minimal compilers which compile a C-like down to asm, though they are very rudimentary compared to more serious projects. I want to emphasize that this is not very meaningful without more details about what you are looking to know.

Here's a compiler for a C-like language written in OCaml (note: I am not one of the authors though I did take the class). Despite it being a college project I think it shows very clean design and particularly good use of preprocessors. All of the details for the language and stuff is linked at the bottom. It's a relatively small codebase of course but I think this is good educationally.

Great! I have not yet made source maps for my programming language that compiles to WebAssembly, and I probably never will.

Up until today, my AEC-to-WebAssembly was, if somebody tried to use two structures of different types as the second and the third operand to the ?: (ternary conditional) operator, as in this example: ``` Structure First Consists Of Nothing; EndStructure

Well, I have written the first compiler for my programming language, targetting x86, in IE6-compatible JavaScript, and the second compiler, targetting WebAssembly, has been written in C++11. I think that, to choose a language to write a compiler in, you need to look at at least two things:

You can see the releases v2.5.3 and v2.5.2 of AECforWebAssembly on GitHub. They are produced with the same version of GCC, the only difference (as far as I know) is that v2.5.2 was produced directly on Debian, whereas v2.5.3 was cross-compiled from Windows to Linux using Docker.

That could be true. I host my AEC-to-WebAssembly compiler on GitHub, GitLab and SourceForge, and it's only on GitHub that it has 21 stars and 2 forks. On GitLab and SourceForge, it has zero of both.

Well, the main compiler for my programming language is targetting the JavaScript Virtual Machine by outputting WebAssembly. I think it's even better than targetting Java Virtual Machine, because, for one thing, your executables can run in any modern browser if you output WebAssembly. If you target Java Virtual Machine, the users need to actually download your app. Furthermore, there is an official assembler for WebAssembly called WebAssembly Binary Toolkit (WABT), so your compiler can output assembly and not have to deal with binary files. There is nothing equivalent to that for Java Virtual Machine.