ocaml
Get flash to fully experience Pearltrees
haXe - Welcome to haXe !
haXe can be compiled to all popular programming platforms with its fast compiler – JavaScript, Flash, NekoVM, PHP, C++, C# and Java (soon) – which means your apps will support all popular mobile devices, such as iOS, Android, Windows Mobile, webOS and more. haXe is open source, which means it’s free , and has the right formula to become the next industry standard as it’s already garnering many adopters in the coding community whom we’d like to fondly call, the haXers! If you are familiar with Java, PHP, JavaScript or ActionScript, the haXe syntax should be very familiar, allowing you to get down to coding right away with a minimal learning curve. Unlike JavaScript which can take hours to debug, haXe has a very strict compile-time type checking feature that allows you to catch errors before testing your program in the browser, and automatically offers helpful instruction on how to debug the issue.
This is a preliminary translation of the book Développement d'applications avec Objective Caml by Emmanuel Chailloux, Pascal Manoury and Bruno Pagano, published by O'Reilly France. The translation is not entirely finished yet; in particular, some solutions to exercises have not been translated yet, and proofreading is not completed. Work continues towards a definitive translation, but we hope that this early release of the translation can be useful. If you notice obvious spelling or grammatical errors, please e-mail translators@pauillac.inria.fr . This translation is the result of a collaborative effort involving about 60 volunteers worldwide. Their names are listed below.
Developing applications with Objective Caml
Lightweight versioning for lightweight protocols | ocaml.janestr
At Jane Street, we often write OCaml programs that communicate over the network with each other, and as such, we need to build lots of little protocols for those programs to use. Macro systems like sexplib and binprot make the generation of such protocols simpler. The basic workflow is to create a module that contains types corresponding to the messages in the protocol. Macros can then be used to generate the serialization and deserialization functions. Just share the protocol module between the different programs that need to communicate with each other, and -- poof -- you have a protocol. This is a highly convenient idiom, and it makes it much easier to quickly throw together a networked application.