caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Malcolm Matalka <mmatalka@gmail.com>
To: Peter Zotov <whitequark@whitequark.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ppx_protobuf
Date: Sat, 03 May 2014 16:08:35 +0000	[thread overview]
Message-ID: <87wqe23kvw.fsf@gmail.com> (raw)
In-Reply-To: <6232dace806569a16f7fbfaa1689ef42@whitequark.org> (Peter Zotov's message of "Fri, 02 May 2014 18:29:55 +0400")

Nice, great work!

I'm not actually a huge fan of mixing type definitions and the protocols
they can be encoded/decoded from.  How hard would it be to take a module
definition accessors on a type and produce a new module with
encode/decode functions?  That way I could create JSON, XML, Protobufs,
etc modules from one module.

Just an idea!

Peter Zotov <whitequark@whitequark.org> writes:

> Greetings.
>
> I have just released the first version of ppx_protobuf, a complete
> Protocol Buffers implementation. Unlike Google's implementation,
> ppx_protobuf derives the message structure directly from OCaml type
> definitions, which allows a much more seamless integration with
> OCaml's types. In particular, ppx_protobuf natively supports
> sum types, while maintaining full backwards compatibility with
> protoc.
>
> ppx_protobuf uses the extension points API, and thus requires
> a recent (>= 2014-04-29) 4.02 (trunk) compiler. It also requires
> an unreleased version of ppx_tools. It is probably easiest
> to install both from the source repositories[1][2].
>
> The API is extensively documented at [3].
>
> [1]: https://github.com/whitequark/ocaml-ppx_protobuf.git
> [2]: https://github.com/alainfrisch/ppx_tools.git
> [3]: https://github.com/whitequark/ocaml-ppx_protobuf/blob/master/README.md
>
> -- 
>   WBR, Peter Zotov.

  reply	other threads:[~2014-05-03 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 14:29 Peter Zotov
2014-05-03 16:08 ` Malcolm Matalka [this message]
2014-05-03 16:24   ` Peter Zotov
2014-05-03 18:46     ` Malcolm Matalka
2014-05-03 18:52       ` Peter Zotov
2014-05-04  4:49         ` Malcolm Matalka
2014-05-04  8:55           ` Peter Zotov
2014-05-04 15:18             ` Malcolm Matalka
2014-05-04 22:21               ` Peter Zotov
2014-05-04 22:38                 ` Daniel Bünzli
2014-05-04 20:34             ` Gerd Stolpmann
2014-05-06  4:29 ` Alain Frisch
2014-05-06  4:59   ` Peter Zotov
2014-05-06  7:33     ` Alain Frisch
2014-05-06 10:42   ` Malcolm Matalka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqe23kvw.fsf@gmail.com \
    --to=mmatalka@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=whitequark@whitequark.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).