Hacker News Reader

Comment by Raphael_Amiard | Hacker News Reader

I wasn't aware of that. The Z3 name was imposed as part of the university project this started with.

It was supposed to be part of the VMKit suite of compilers, J3 being the Java bytecode compiler and N3 being the .Net compiler.

I'd be happy to change the name of this project if it ever gains enough traction to cause confusion in any way :)

View on HN

To backup the original poster, one of OCaml's stronger communities focuses on program analysis for C programs (using the CIL library http://www.cs.berkeley.edu/~necula/cil/) and SMT solvers like Z3 are also widely used in that community, so there's definitely some potential for confusion if your OCaml backend gains some traction.

Still, an LLVM backend for OCaml seems like a great idea. Keep up the good work.

> I'd be happy to change the name of this project if it ever gains enough traction to cause confusion in any way :)

By that time it is largely too late and the damage/bother is already difficult to fix.

Ha I didn't recognize the VMKit name, but since I googled some things, and found this project, in case someone is interested : http://vmkit2.gforge.inria.fr/index.php

If Java gets J3 and .NET gets N3, why doesn't OCaml get O3? It's also a cute name because it looks just like an optimization level :).

Is it in collaboration with the core ocaml team ? or at least are they aware of it ?

If you're following J3 and N3, then why not O3?

Or OCamLLVM? ;)

Reply on news.ycombinator.com