# Format strings and the OCaml compiler error messages

**URL:** <https://discuss.ocaml.org/t/format-strings-and-the-ocaml-compiler-error-messages/11870>\
**Category:** Community\
**Created:** [April 3, 2023, 3:54pm UTC](https://discuss.ocaml.org/t/format-strings-and-the-ocaml-compiler-error-messages/11870 "2023-04-03T15:54:24Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![octachron](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@octachron](https://discuss.ocaml.org/u/octachron)\
**Post date:** [April 3, 2023, 3:54pm UTC](https://discuss.ocaml.org/t/format-strings-and-the-ocaml-compiler-error-messages/11870/1 "2023-04-03T15:54:24Z")

</div>

I am currently trying my hand at writing down my weekly activity on the OCaml compiler as blog post on the Cambium team blog:

[http://gallium.inria.fr/blog/florian-weekly-2023-04-03](http://gallium.inria.fr/blog/florian-weekly-2023-04-03)

This week the main and only topics is some ongoing work on mine on an alternative handling for partial error messages in the compiler. The medium-term objective is to move slowly towards machine-readable error message by making that all the type used in error report internally in the compiler are serializable. This has lead towards a fun path of implementing an alternative format string interpreter that you can see in action at [GitHub - Octachron/format-doc: Alternative interpreter for OCaml format strings](https://github.com/Octachron/format-doc) .

---

_[View the full topic](https://discuss.ocaml.org/t/format-strings-and-the-ocaml-compiler-error-messages/11870)._